<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Cygwin/X Frequently Asked Questions</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"/><LINK
REL="NEXT"
TITLE="Bibliography"
HREF="biblio.html"/><META
HTTP-EQUIV="Content-Type"
CONTENT="text/html;charset=utf-8"/></HEAD
><BODY
CLASS="article"
><DIV
CLASS="ARTICLE"
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="title"
><A
NAME="article-info"
>Cygwin/X Frequently Asked Questions</A
></H1
><H2
CLASS="subtitle"
>2016-08-30 16:53</H2
><HR/></DIV
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
><A
HREF="cygwin-x-faq.html#qanda"
>Questions and Answers</A
></DT
><DT
><A
HREF="biblio.html"
>Bibliography</A
></DT
><DT
><A
HREF="glossary.html"
>Glossary</A
></DT
><DT
>A. <A
HREF="gfdl.html"
>GNU Free Documentation License</A
></DT
></DL
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="qanda"
>Questions and Answers</A
></H1
><DIV
CLASS="qandaset"
><DL
><DT
>1. <A
HREF="cygwin-x-faq.html#general"
>General Information</A
></DT
><DD
><DL
><DT
>1.1. <A
HREF="cygwin-x-faq.html#q-what-is-cygwin-x"
>What is Cygwin/X?</A
></DT
><DT
>1.2. <A
HREF="cygwin-x-faq.html#q-what-is-cygwin"
>What is Cygwin?</A
></DT
><DT
>1.3. <A
HREF="cygwin-x-faq.html#q-what-is-x-window-system"
>What is the X Window System?</A
></DT
><DT
>1.4. <A
HREF="cygwin-x-faq.html#q-what-is-x-server"
>What is an X Server?</A
></DT
><DT
>1.5. <A
HREF="cygwin-x-faq.html#q-what-is-x-client"
>What is an X client?</A
></DT
><DT
>1.6. <A
HREF="cygwin-x-faq.html#display-and-screen"
>What does DISPLAY=:0.0 mean?</A
></DT
><DT
>1.7. <A
HREF="cygwin-x-faq.html#q-why-port-to-windows"
>Why port the X Window System to Microsoft Windows?</A
></DT
><DT
>1.8. <A
HREF="cygwin-x-faq.html#q-newsgroup"
>Is there a Cygwin/X newsgroup?</A
></DT
><DT
>1.9. <A
HREF="cygwin-x-faq.html#q-mailing-list"
>Is there a Cygwin/X mailing list?</A
></DT
></DL
></DD
><DT
>2. <A
HREF="cygwin-x-faq.html#installation"
>Installation</A
></DT
><DD
><DL
><DT
>2.1. <A
HREF="cygwin-x-faq.html#q-windows-versions-supported"
>What versions of Windows does Cygwin/X run on?</A
></DT
><DT
>2.2. <A
HREF="cygwin-x-faq.html#q-how-to-install"
>How is Cygwin/X installed?</A
></DT
><DT
>2.3. <A
HREF="cygwin-x-faq.html#q-cant-read-lock-file"
>Fatal server error: Can't read lock file /tmp/.X0-lock</A
></DT
><DT
>2.4. <A
HREF="cygwin-x-faq.html#q-startxwin-no-windows"
>&#13;Nothing appears to happen when I try to start the X server using the "XWin Server" start menu shortcut.
</A
></DT
></DL
></DD
><DT
>3. <A
HREF="cygwin-x-faq.html#modular"
>Upgrade</A
></DT
><DD
><DL
><DT
>3.1. <A
HREF="cygwin-x-faq.html#q-x-is-broke"
>What happened to my X server? Where did <TT
CLASS="filename"
>/usr/X11R6/</TT
> go?
</A
></DT
><DT
>3.2. <A
HREF="cygwin-x-faq.html#q-i-cant-type-anything"
>I upgraded my X server and now I can't type anything into any X application</A
></DT
><DT
>3.3. <A
HREF="cygwin-x-faq.html#q-whereis-startxwin-bat"
>I can't find <B
CLASS="command"
>startxwin.bat</B
> or <B
CLASS="command"
>startxwin.exe</B
> to start the X server</A
></DT
><DT
>3.4. <A
HREF="cygwin-x-faq.html#q-moved-1"
>Moved question</A
></DT
><DT
>3.5. <A
HREF="cygwin-x-faq.html#q-where-are-my-fonts"
>My favourite font has gone! The font Emacs uses is just boxes</A
></DT
><DT
>3.6. <A
HREF="cygwin-x-faq.html#q-where-is-xxyzy"
>Where has <B
CLASS="command"
>xhost</B
>/<B
CLASS="command"
>xlsfonts</B
>/etc. gone?</A
></DT
><DT
>3.7. <A
HREF="cygwin-x-faq.html#q-how-do-i-get-rid-of-xterm-menu"
>How do I get rid of that menu at the top of my xterm?</A
></DT
><DT
>3.8. <A
HREF="cygwin-x-faq.html#q-ssh-y"
>ssh -X now says "Warning: untrusted X11 forwarding setup failed: xauth key data not generated"</A
></DT
><DT
>3.9. <A
HREF="cygwin-x-faq.html#q-nedit-wont-start"
>&#13;<B
CLASS="command"
>nedit</B
> fails to start with an error message 
</A
></DT
><DT
>3.10. <A
HREF="cygwin-x-faq.html#q-startx-is-has-root-window"
>&#13;I start my X server with <B
CLASS="command"
>startx</B
> or <B
CLASS="command"
>xinit</B
> and now all my X windows are contained within one large root Windows window?  How do I get it back to each X window in it's own Windows window?
</A
></DT
><DT
>3.11. <A
HREF="cygwin-x-faq.html#q-moved-2"
>Moved question</A
></DT
><DT
>3.12. <A
HREF="cygwin-x-faq.html#q-startxwinrc-exit"
>I upgraded and now X exits immediately after starting</A
></DT
><DT
>3.13. <A
HREF="cygwin-x-faq.html#q-xserver-nolisten-tcp-default"
>I upgraded and now X clients can't connect</A
></DT
></DL
></DD
><DT
>4. <A
HREF="cygwin-x-faq.html#configuration"
>Configuration</A
></DT
><DD
><DL
><DT
>4.1. <A
HREF="cygwin-x-faq.html#q-why-no-xf86config"
>Is there an xorg.conf or XF86Config file?</A
></DT
><DT
>4.2. <A
HREF="cygwin-x-faq.html#q-command-line-args"
>What are the command line options for <TT
CLASS="filename"
>X</TT
>? How do I add command line options for <TT
CLASS="filename"
>X</TT
>?</A
></DT
><DT
>4.3. <A
HREF="cygwin-x-faq.html#q-display-depth-ignored"
>Why does <TT
CLASS="filename"
>X</TT
> ignore the display depth that I pass
on the command line?</A
></DT
><DT
>4.4. <A
HREF="cygwin-x-faq.html#q-three-button-emulation"
>I have a two button mouse, can I emulate a three button mouse?</A
></DT
><DT
>4.5. <A
HREF="cygwin-x-faq.html#window-auto-focus"
>Is there a Focus-Follows-Mouse feature (Auto-Focus)?</A
></DT
><DT
>4.6. <A
HREF="cygwin-x-faq.html#disable-terminate-server"
>The option -nounixkill has no effect. How can i prevent the server 
shutdown an Ctrl-Alt-BackSpace?</A
></DT
><DT
>4.7. <A
HREF="cygwin-x-faq.html#q-multihead"
>I have a multihead system. Do I need special options to make it work?
I have a multihead system.  Why are my X-application windows white?</A
></DT
><DT
>4.8. <A
HREF="cygwin-x-faq.html#q-firewall"
>I have a firewall. Is there anything I have to take care of?
</A
></DT
></DL
></DD
><DT
>5. <A
HREF="cygwin-x-faq.html#i18n"
>Internationalization</A
></DT
><DD
><DL
><DT
>5.1. <A
HREF="cygwin-x-faq.html#i18n-keyboard"
>Keyboard support</A
></DT
><DD
><DL
><DT
>5.1.1. <A
HREF="cygwin-x-faq.html#q-non-U.S.-keyboard-layout"
>How do I use a non-U.S. keyboard layout?</A
></DT
><DT
>5.1.2. <A
HREF="cygwin-x-faq.html#q-submit-layout"
>Is there a way to add a layout to the list of autodetected layouts?</A
></DT
><DT
>5.1.3. <A
HREF="cygwin-x-faq.html#q-modmap-obtaining"
>Where can I find an xmodmap for my non-U.S. keyboard layout?</A
></DT
><DT
>5.1.4. <A
HREF="cygwin-x-faq.html#q-how-modmap-and-xdmcp"
>How do I get my non-U.S. keyboard modmap to be installed when
using xdmcp?</A
></DT
><DT
>5.1.5. <A
HREF="cygwin-x-faq.html#q-aix-xkb"
>Logging into AIX via XDMCP causes the keyboard to function as if
<B
CLASS="keycap"
>AltGr</B
> is permanently pressed.</A
></DT
><DT
>5.1.6. <A
HREF="cygwin-x-faq.html#q-xkb-not-working"
>Loading an XKB keyboard layout selected with -xkblayout fails</A
></DT
><DT
>5.1.7. <A
HREF="cygwin-x-faq.html#alt-gr-win-xp-powertoys"
>I have Windows XP with Powertoys installed and AltGr does not work. 
What can I do?</A
></DT
><DT
>5.1.8. <A
HREF="cygwin-x-faq.html#alt-gr-with-old-x"
>AltGr does not work properly when connecting to various older commercial unices
(e.g. HP-UX, AIX) or to old XFree86.</A
></DT
></DL
></DD
><DT
>5.2. <A
HREF="cygwin-x-faq.html#i18n-display"
>Display problems</A
></DT
><DD
><DL
><DT
>5.2.1. <A
HREF="cygwin-x-faq.html#q-bash-extended-chars"
>How do I get <B
CLASS="command"
>bash</B
> to display accents and/or
umlauts?</A
></DT
><DT
>5.2.2. <A
HREF="cygwin-x-faq.html#q-bash-8bit"
>How do I put <B
CLASS="command"
>bash</B
> into <SPAN
CLASS="QUOTE"
>"8 bit"</SPAN
>
mode?</A
></DT
><DT
>5.2.3. <A
HREF="cygwin-x-faq.html#q-xterm-utf8"
>How do I display unicode characters in an <B
CLASS="command"
>xterm</B
>?
</A
></DT
></DL
></DD
></DL
></DD
><DT
>6. <A
HREF="cygwin-x-faq.html#remote"
>Remote connections</A
></DT
><DD
><DL
><DT
>6.1. <A
HREF="cygwin-x-faq.html#q-ssh-no-x11forwarding"
>X11Forwarding does not work with OpenSSH under Cygwin</A
></DT
><DT
>6.2. <A
HREF="cygwin-x-faq.html#q-bad-atom"
>Why do remote programs crash with an <SPAN
CLASS="errorname"
>X Error of failed request: BadAtom</SPAN
>?
Why do remote programs exit when you try to copy and paste?
</A
></DT
><DT
>6.3. <A
HREF="cygwin-x-faq.html#q-trusted-untrusted-x11-forwarding"
>I'm confused about the difference between trusted and untrusted X11 forwarding.
What does "Warning: untrusted X11 forwarding setup failed: xauth key data not generated" mean?
Why is the SECURITY extension disabled?
</A
></DT
><DT
>6.4. <A
HREF="cygwin-x-faq.html#q-warning-no-xauth-data"
>&#13;What does "Warning: no xauth data; using fake authentication data for X11 forwarding" mean?
</A
></DT
><DT
>6.5. <A
HREF="cygwin-x-faq.html#q-twenty-minute-timeout"
>&#13;Why can't new remote X clients connect to the X server after 20 minutes?
</A
></DT
><DT
>6.6. <A
HREF="cygwin-x-faq.html#q-remote-clients-cant-connect"
>&#13;Remote clients can't connect
</A
></DT
><DT
>6.7. <A
HREF="cygwin-x-faq.html#q-local-noncygwin-clients-cant-connect"
>&#13;X sessions forwarded by <B
CLASS="command"
>PuTTY</B
> can't connect.
Non-cygwin local X clients can't connect.
</A
></DT
></DL
></DD
><DT
>7. <A
HREF="cygwin-x-faq.html#xdmcp"
>XDMCP connections</A
></DT
><DD
><DL
><DT
>7.1. <A
HREF="cygwin-x-faq.html#q-xdmcp-no-valid-address"
><SPAN
CLASS="errorname"
>XDMCP fatal error: Session declined No valid
address</SPAN
></A
></DT
><DT
>7.2. <A
HREF="cygwin-x-faq.html#q-audit-client-rejected"
>Why does Cygwin/X report AUDIT: client 1 rejected from IP 
<TT
CLASS="replaceable"
><I
>remotehost</I
></TT
>?</A
></DT
><DT
>7.3. <A
HREF="cygwin-x-faq.html#q-xdmcp-query"
>I get no login screen when using <CODE
CLASS="parameter"
>-query</CODE
></A
></DT
><DT
>7.4. <A
HREF="cygwin-x-faq.html#q-mandrake-8.1-xdmcp"
>XDMCP does not work with Mandrake 8.1</A
></DT
><DT
>7.5. <A
HREF="cygwin-x-faq.html#q-xdmcp-gdm"
>Why does GDM not work with <CODE
CLASS="parameter"
>-clipboard</CODE
></A
></DT
><DT
>7.6. <A
HREF="cygwin-x-faq.html#q-solaris-fonts"
>I get no login screen for Solaris</A
></DT
><DT
>7.7. <A
HREF="cygwin-x-faq.html#q-remote-solaris"
>XDMCP freezes with remote Solaris machine!</A
></DT
><DT
>7.8. <A
HREF="cygwin-x-faq.html#q-cde-via-xdmcp-hangs"
>Login to <ACRONYM
CLASS="acronym"
>CDE</ACRONYM
> on Solaris via XDMCP hangs
Cygwin/X.</A
></DT
><DT
>7.9. <A
HREF="cygwin-x-faq.html#q-xdmcp-info"
>Where can I find more information about XDMCP.</A
></DT
></DL
></DD
><DT
>8. <A
HREF="cygwin-x-faq.html#troubleshooting"
>Troubleshooting</A
></DT
><DD
><DL
><DT
>8.1. <A
HREF="cygwin-x-faq.html#q-fatal-error"
>Cygwin/X failed with "Fatal Error". What does this mean?</A
></DT
><DT
>8.2. <A
HREF="cygwin-x-faq.html#q-log-file-location"
>Is there a log file that I can look at for diagnostic
information and error messages?</A
></DT
><DT
>8.3. <A
HREF="cygwin-x-faq.html#q-error-message-interpretation"
>I have a specific error message, what does it mean?</A
></DT
><DT
>8.4. <A
HREF="cygwin-x-faq.html#q-error-message-not-listed"
>I have a specific error message that is not addressed in the
Error and Warning Messages section.</A
></DT
><DT
>8.5. <A
HREF="cygwin-x-faq.html#q-but-report-ignored"
>My bug report the Cygwin/X mailing list was ignored.  What do I
do now?</A
></DT
><DT
>8.6. <A
HREF="cygwin-x-faq.html#freeze-at-startup"
>Why does Cygwin/X freeze right after startup?</A
></DT
><DT
>8.7. <A
HREF="cygwin-x-faq.html#poor-performance"
>Cygwin/X has very poor performance. What's the reason?</A
></DT
><DT
>8.8. <A
HREF="cygwin-x-faq.html#microsoft-services-for-unix"
>I have Microsoft Services for Unix installed and can't type anything. 
Help me!!!</A
></DT
><DT
>8.9. <A
HREF="cygwin-x-faq.html#q-tasklist-programs-slow"
>Cygwin/X is extremely slow, especially when using XDMCP to
connect to remote machines.</A
></DT
><DT
>8.10. <A
HREF="cygwin-x-faq.html#q-trackpoint"
>Simulated mouse wheel scrolling doesn't work with a TrackPoint mouse
(found on IBM laptops) or Synaptics Touchpads</A
></DT
><DT
>8.11. <A
HREF="cygwin-x-faq.html#no-rootwindow-with-run"
>Why is the root window not shown in normal mode?</A
></DT
><DT
>8.12. <A
HREF="cygwin-x-faq.html#cross-as-pointer"
>Why is the cross the default cursor in multiwindow mode?</A
></DT
><DT
>8.13. <A
HREF="cygwin-x-faq.html#xterm-not-resizing"
>How can I adjust the linewidth in bash after resizing XTerm?</A
></DT
><DT
>8.14. <A
HREF="cygwin-x-faq.html#numlock-modifier"
>Why do some menus not work if Num-Lock is on?</A
></DT
></DL
></DD
><DT
>9. <A
HREF="cygwin-x-faq.html#errors"
>Error and Warning Messages</A
></DT
><DD
><DL
><DT
>9.1. <A
HREF="cygwin-x-faq.html#q-owner-tmp-.X11-unix"
><SPAN
CLASS="errorname"
>_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root</SPAN
></A
></DT
><DT
>9.2. <A
HREF="cygwin-x-faq.html#q-error-security-policy"
><SPAN
CLASS="errorname"
>error opening security policy file
/usr/X11R6/lib/X11/xserver/SecurityPolicy</SPAN
></A
></DT
><DT
>9.3. <A
HREF="cygwin-x-faq.html#duplicate-invocation"
>Duplicate invocation on display number: 0.  Exiting.</A
></DT
><DT
>9.4. <A
HREF="cygwin-x-faq.html#q-error-font-eof"
><SPAN
CLASS="errorname"
>Fatal server error: could not open default font
'fixed'</SPAN
></A
></DT
><DT
>9.5. <A
HREF="cygwin-x-faq.html#q-removing-font-path-element"
><SPAN
CLASS="errorname"
>Could not init font path element
/usr/share/fonts/<TT
CLASS="replaceable"
><I
>*</I
></TT
>/, removing from
list!</SPAN
></A
></DT
><DT
>9.6. <A
HREF="cygwin-x-faq.html#q-procedure-entry-point-missing"
><SPAN
CLASS="errorname"
>The procedure entry point _check_for_executable could
not be located</SPAN
></A
></DT
><DT
>9.7. <A
HREF="cygwin-x-faq.html#cygX11-6.dll-missing"
>cygX11-6.dll not found after installation or upgrade</A
></DT
><DT
>9.8. <A
HREF="cygwin-x-faq.html#q-status-access-violation"
><SPAN
CLASS="errorname"
>Exception: STATUS_ACCESS_VIOLATION</SPAN
></A
></DT
><DT
>9.9. <A
HREF="cygwin-x-faq.html#q-error-max-clients"
><SPAN
CLASS="errorname"
>Xlib: connection to
"<TT
CLASS="replaceable"
><I
>local_host_name_or_ip_address</I
></TT
>:0.0" refused
by server Xlib: Maximum number of clients reached</SPAN
></A
></DT
><DT
>9.10. <A
HREF="cygwin-x-faq.html#q-xio-fatal-io-error-104"
><SPAN
CLASS="errorname"
>XIO: fatal IO error 104 (Connection reset by peer) on
 X server "127.0.0.1:0.0"</SPAN
></A
></DT
><DT
>9.11. <A
HREF="cygwin-x-faq.html#q-cannot-open-display"
><SPAN
CLASS="errorname"
>Cannot Open Display: 127.0.0.1:0.0</SPAN
></A
></DT
><DT
>9.12. <A
HREF="cygwin-x-faq.html#q-error-env-space"
>Out of environment space</A
></DT
><DT
>9.13. <A
HREF="cygwin-x-faq.html#q-too-many-parameters"
>Too many parameters</A
></DT
><DT
>9.14. <A
HREF="cygwin-x-faq.html#q-xcb-lock-assertion"
>&#13;"xcb_xlib_lock: Assertion '!c-&gt;xlib.lock' failed." or "xcb_xlib_unlock: Assertion 'c-&gt;xlib.lock' failed."
</A
></DT
><DT
>9.15. <A
HREF="cygwin-x-faq.html#q-failed-to-compile-keymap"
>Fatal server error: Failed to activate core devices.</A
></DT
><DT
>9.16. <A
HREF="cygwin-x-faq.html#q-fork-failures"
>"fatal error - unable to remap (some dll) to same address as parent: (some hex number) != (some other hex number)" or
"(some dll): Loaded to different address: parent(some hex number) != child(some other hex number)"</A
></DT
><DT
>9.17. <A
HREF="cygwin-x-faq.html#q-died-waiting-for-longjmp"
>fork: child -1 - died waiting for longjmp before initialization, retry (some number), exit code (some hex number), errno (some other number)</A
></DT
></DL
></DD
><DT
>10. <A
HREF="cygwin-x-faq.html#porting"
>Porting Software</A
></DT
><DD
><DL
><DT
>10.1. <A
HREF="cygwin-x-faq.html#q-ported-software-list"
>Is there a list of software that has been ported to Cygwin/X?</A
></DT
><DT
>10.2. <A
HREF="cygwin-x-faq.html#q-how-to-port"
>How do I start porting software to Cygwin/X?</A
></DT
><DT
>10.3. <A
HREF="cygwin-x-faq.html#q-common-porting-problems"
>Are there common problems encountered when porting software to
Cygwin/X?</A
></DT
><DT
>10.4. <A
HREF="cygwin-x-faq.html#q-opengl-link-problems"
>Problems linking OpenGL applications? Undefined reference to _gl<SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>something</I
></SPAN
>?</A
></DT
></DL
></DD
><DT
>11. <A
HREF="cygwin-x-faq.html#contributing"
>Contributing</A
></DT
><DD
><DL
><DT
>11.1. <A
HREF="cygwin-x-faq.html#q-instructions-for-contributing"
>Are there step-by-step instructions for contributing to
Cygwin/X?</A
></DT
><DT
>11.2. <A
HREF="cygwin-x-faq.html#q-editors"
>Are there editors for Windows that understand and
preserve <ACRONYM
CLASS="acronym"
>UNIX</ACRONYM
> end of line characters?</A
></DT
><DT
>11.3. <A
HREF="cygwin-x-faq.html#q-contrib-diff"
>How should I generate patches for Cygwin/X?</A
></DT
><DT
>11.4. <A
HREF="cygwin-x-faq.html#q-where-to-submit-patches"
>Where do I submit patches for Cygwin/X?</A
></DT
><DT
>11.5. <A
HREF="cygwin-x-faq.html#q-why-no-autoconf"
>Why doesn't the X Window System use GNU's
<B
CLASS="command"
>autoconf</B
>?</A
></DT
><DT
>11.6. <A
HREF="cygwin-x-faq.html#q-which-compilers-supported"
>What compiler does Cygwin/X use, and which compilers are
supported?</A
></DT
><DT
>11.7. <A
HREF="cygwin-x-faq.html#q-cross-compiling"
>Is cross-compiling from a non-Cygwin platform supported?</A
></DT
><DT
>11.8. <A
HREF="cygwin-x-faq.html#q-help-installing-docbook"
>Where can I get help for installing DocBook on Cygwin?</A
></DT
></DL
></DD
><DT
>12. <A
HREF="cygwin-x-faq.html#license-ptc"
>Licenses, Patents, Trademarks, and Copyrights</A
></DT
><DD
><DL
><DT
>12.1. <A
HREF="cygwin-x-faq.html#q-what-licenses-apply"
>What licenses apply to Cygwin/X source code?</A
></DT
><DT
>12.2. <A
HREF="cygwin-x-faq.html#q-license-x-window-system"
>What licenses apply to the X Window System source code?</A
></DT
><DT
>12.3. <A
HREF="cygwin-x-faq.html#q-license-cygwin"
>What license applies to Cygwin source code?</A
></DT
><DT
>12.4. <A
HREF="cygwin-x-faq.html#q-copyright-cygwin-x"
>Who holds the copyright on the Cygwin/X source code?</A
></DT
><DT
>12.5. <A
HREF="cygwin-x-faq.html#q-copyright-x-window-system"
>Who holds the copyright on the X Window System source code?</A
></DT
><DT
>12.6. <A
HREF="cygwin-x-faq.html#q-copyright-cygwin"
>Who holds the copyright on the Cygwin source code?</A
></DT
><DT
>12.7. <A
HREF="cygwin-x-faq.html#q-motif-license"
>What license applies to Motif?</A
></DT
><DT
>12.8. <A
HREF="cygwin-x-faq.html#q-trademark-xwin"
>Isn't <SPAN
CLASS="QUOTE"
>"XWin"</SPAN
> trademarked by StarNet Communications?</A
></DT
></DL
></DD
></DL
><DIV
CLASS="qandadiv"
><H3
><A
NAME="general"
></A
>1. General Information</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-what-is-cygwin-x"
></A
><B
>1.1. </B
>What is Cygwin/X?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Cygwin/X is a port of the X Window System to Cygwin. 
Cygwin provides a <ACRONYM
CLASS="acronym"
>UNIX</ACRONYM
>-like API on the Win32 platform.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-what-is-cygwin"
></A
><B
>1.2. </B
>What is Cygwin?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Cygwin tools are, in the words of the
<A
HREF="http://cygwin.com/faq.html#faq.what"
TARGET="_top"
>Cygwin FAQ</A
>,
<SPAN
CLASS="QUOTE"
>"
ports of the popular GNU development tools and utilities for Microsoft Windows.
They run thanks to the Cygwin library which provides the POSIX system calls
and environment these programs expect. 
"</SPAN
>
Cygwin provides the compiler (gcc), libraries, headers, and other
utilities which build and support the operation of Cygwin/X.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-what-is-x-window-system"
></A
><B
>1.3. </B
>What is the X Window System?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
><SPAN
CLASS="attribution"
>[<SPAN
CLASS="citation"
>ScheiflerGettys92</SPAN
>]</SPAN
><P
>The X Window System, or X, is a network-transparent window system.
With X, multiple applications can run simultaneously in windows,
generating text and graphics in monochrome or color on a bitmap
display.  Network transparency means that application programs can run
on machines scattered through the network.</P
></P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-what-is-x-server"
></A
><B
>1.4. </B
>What is an X Server?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>An X Server is a program that provides display and user input
services to other programs.  In comparison, a file server provides
other programs with access to file storage devices.  File servers are
typically located in a remote location and you use the services of a
file server from the machine that you are located at.  In contrast, an
X Server is typically running on the machine that you are located at;
display and user input services may be requested by programs running
on your machine, as well as by programs running on remote
machines.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-what-is-x-client"
></A
><B
>1.5. </B
>What is an X client?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>An X client is a program that utilizes the display and user
input services provided by an X Server.  X clients may run on the same
or disparate machine as the X Server that is providing display and
user input services.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="display-and-screen"
></A
><B
>1.6. </B
>What does DISPLAY=:0.0 mean?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
The <CODE
CLASS="parameter"
>DISPLAY</CODE
> environment variable instructs an X client which X server it
is to connect to by default.  Typically this can be overriden by running
the client with a <CODE
CLASS="parameter"
>-display</CODE
> or <CODE
CLASS="parameter"
>-d</CODE
>
command line option.
</P
><P
>The <TT
CLASS="replaceable"
><I
>:0.0</I
></TT
> part of the <CODE
CLASS="parameter"
>DISPLAY</CODE
> variable denote
the display and the screen of an X server.</P
><P
>The display is the first number and should equal the display number
given to a running instance of an X server.  By default the X server uses
display number 0.
If the X server is using TCP/IP for communication it listens on port 6000 + 
<TT
CLASS="replaceable"
><I
>display-number</I
></TT
> for X client connections.
For local (UNIX domain sockets) it uses the socket 
<TT
CLASS="filename"
>/tmp/.X11-unix/X<TT
CLASS="replaceable"
><I
>display-number</I
></TT
></TT
>
</P
><P
> The screen denotes different output devices of the X server. You could 
start <TT
CLASS="filename"
>X</TT
> with two <CODE
CLASS="parameter"
>-screen</CODE
> options and would end up 
with two X11 windows. Each of them is a different screen. Other X servers open
different screens for different monitors connected to the computer.</P
><P
>Cygwin/X supports different formats of the <CODE
CLASS="parameter"
>DISPLAY</CODE
> variable
<UL
><LI
><P
>&#13;<TT
CLASS="replaceable"
><I
>:0.0</I
></TT
> or <TT
CLASS="replaceable"
><I
>unix:0.0</I
></TT
>
</P
><P
>&#13;This names a local X server and the communication uses the UNIX domain sockets.
</P
></LI
><LI
><P
>&#13;<TT
CLASS="replaceable"
><I
>hostname:0.0</I
></TT
>
</P
><P
>&#13;This names a remote X server and the communication uses the TCP/IP network.
</P
></LI
></UL
>
</P
><P
>&#13;See the DISPLAY NAMES section of <B
CLASS="command"
>man X</B
> for more information.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-why-port-to-windows"
></A
><B
>1.7. </B
>Why port the X Window System to Microsoft Windows?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Porting X Window System to Microsoft Windows benefits many
people and projects in many ways:</P
><UL
><LI
><P
>Prior to Cygwin/X only commercial, closed source X Servers were
available for Microsoft Windows.</P
></LI
><LI
><P
>An X Server on Windows may be used to display the output of
programs running on remote <ACRONYM
CLASS="acronym"
>UNIX</ACRONYM
> machines.</P
></LI
><LI
><P
>Cygwin/X, in conjunction with Cygwin, provides a complete
compatibility layer for compiling and running <ACRONYM
CLASS="acronym"
>UNIX</ACRONYM
>
applications on Microsoft Windows.</P
></LI
></UL
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-newsgroup"
></A
><B
>1.8. </B
>Is there a Cygwin/X newsgroup?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>No, Cygwin/X does not have a newsgroup; however, we do have a
mailing list.  See <A
HREF="cygwin-x-faq.html#q-mailing-list"
>Q: 1.9.</A
></P
><P
>You can read and post to the mailing list using your newsreader
using the <A
HREF="http://gmane.org/find.php?list=os.cygwin"
TARGET="_top"
>GMANE</A
>
mail-to-news gateway.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-mailing-list"
></A
><B
>1.9. </B
>Is there a Cygwin/X mailing list?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Yes, Cygwin/X is on-topic for the cygwin@cygwin.com mailing list.
Non-subscribers may post to this list.
Visit the <A
HREF="http://cygwin.com/lists.html"
TARGET="_top"
>Cygwin Mailing Lists</A
>
page to subscribe to cygwin@cygwin.com as well as to read and search an
online archive of the mailing list traffic.</P
></DIV
></DIV
></DIV
><DIV
CLASS="qandadiv"
><H3
><A
NAME="installation"
></A
>2. Installation</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-windows-versions-supported"
></A
><B
>2.1. </B
>What versions of Windows does Cygwin/X run on?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Cygwin/X aims to support all versions of Windows supported by
Cygwin.</P
><P
>However, Cygwin/X is not tested on older versions of Windows
(i.e. Windows NT4, Windows 2000) and may be broken. Problem reports are welcomed.
</P
><P
>Cygwin/X requires Cygwin to compile and run.  Cygwin is
not, as of writing, available on Microsoft Windows CE, therefore
Cygwin/X is not currently available on Microsoft Windows CE.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-how-to-install"
></A
><B
>2.2. </B
>How is Cygwin/X installed?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>The <A
HREF="http://x.cygwin.com/docs/ug/cygwin-x-ug.html"
TARGET="_top"
>Cygwin/X User's Guide</A
>
thoroughly documents the installation process.  Installation is
performed through Cygwin's setup
program.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-cant-read-lock-file"
></A
><B
>2.3. </B
>Fatal server error: Can't read lock file /tmp/.X0-lock</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>This question should be obsolete.</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
A1: /tmp resides on a FAT filesystem
</P
><P
>Start the server with the <CODE
CLASS="parameter"
>-nolock</CODE
> option.  See <A
HREF="cygwin-x-faq.html#q-command-line-args"
>Q: 4.2.</A
></P
><P
>&#13;You should really consider updating the filesystem to NTFS using Microsoft's <B
CLASS="command"
>convert.exe</B
> tool.
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
A2: /tmp resides on a NTFS filesystem.
</P
><P
>&#13;This can be caused by a stale lock file being left behind after the X server is run by a user with
Adminstrator rights, which cannot be overwritten when the X server is next run by a user without
Adminstrator rights.
</P
><P
>&#13;Failure to clean up the lock file properly is a bug in the X server, but until that is fixed the
following workarounds may be neccessary.
</P
><OL
COMPACT="COMPACT"
TYPE="1"
><LI
><P
>Try removing the stale lock file using
<B
CLASS="command"
>rm -f /tmp/.X<TT
CLASS="replaceable"
><I
>n</I
></TT
>-lock</B
>
where <TT
CLASS="replaceable"
><I
>n</I
></TT
> is the display number.
If this fails due to insufficent permissions, you must either get the owner or a user with Adminstrator rights to
remove the stale lock file.
</P
></LI
><LI
><P
>Try starting the server with the <CODE
CLASS="parameter"
>-nolock</CODE
> option. (See <A
HREF="cygwin-x-faq.html#q-command-line-args"
>Q: 4.2.</A
>)</P
></LI
></OL
><P
>Technical details:
The X server attempts to create a lock file in
<TT
CLASS="filename"
>/tmp</TT
> by creating the file under a temporary name,
then renaming it to the proper name (by hard linking it under the correct name, then unlinking
it from the temporary name). If this rename fails it attempts to read the existing
lock file to determine the pid of an already running server.

The FAT filesystem does not support hardlinks so this operation cannot succeed.

On NFTS filesystems, the failure case appears to be that lock file was created successfully, but
the rename failed due to a stale lock file created by a user with Adminstrator rights.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-startxwin-no-windows"
></A
><B
>2.4. </B
>
Nothing appears to happen when I try to start the X server using the "XWin Server" start menu shortcut.
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
A1:
</P
><P
>This answer should be obsolete.</P
><P
>&#13;Task manager shows the <B
CLASS="command"
>startxwin.exe</B
> process starting, spawning <B
CLASS="command"
>XWin.exe</B
>
and <B
CLASS="command"
>xterm.exe</B
>, but no windows are shown.  Running <B
CLASS="command"
>startxwin.exe</B
> from
a bash shell works correctly.
This is caused by having <CODE
CLASS="parameter"
>tty</CODE
> in the <CODE
CLASS="parameter"
>CYGWIN</CODE
> environment variable
set through the Windows control panel.  Removing <CODE
CLASS="parameter"
>tty</CODE
> resolves this issue.
</P
><P
>&#13;If you really need <CODE
CLASS="parameter"
>CYGWIN=tty</CODE
> for working with <B
CLASS="command"
>cmd.exe</B
> windows,
you'll have to arrange to set that by some other means before invoking <B
CLASS="command"
>cygwin.bat</B
>.
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
A2:
</P
><P
>&#13;Try running <B
CLASS="command"
>startxwin</B
> from a <B
CLASS="command"
>bash</B
> shell
in the <B
CLASS="command"
>mintty</B
> terminal emulator,
it should output some error message which should indicate why it's not able to start.
</P
><DIV
CLASS="note"
><BLOCKQUOTE
CLASS="note"
><P
><B
>Note: </B
>
For technical reasons, the output of XWin doesn't appear in <B
CLASS="command"
>cmd.exe</B
> windows unless
the <CODE
CLASS="parameter"
>CYGWIN</CODE
> environment variable set through the Windows control panel contains
<CODE
CLASS="parameter"
>tty</CODE
>, so to ensure the output can be seen, use <B
CLASS="command"
>mintty</B
>.
</P
></BLOCKQUOTE
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="qandadiv"
><H3
><A
NAME="modular"
></A
>3. Upgrade</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-x-is-broke"
></A
><B
>3.1. </B
>What happened to my X server? Where did <TT
CLASS="filename"
>/usr/X11R6/</TT
> go?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>The upgrade from X.Org R6.8 to modular X.Org R7.4 made a lot of changes.
Please
<A
HREF="http://cygwin.com/ml/cygwin-xfree-announce/2008-11/msg00000.html"
TARGET="_top"
>&#13;read the announce email</A
>
and pay attention to the upgrade instructions
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-i-cant-type-anything"
></A
><B
>3.2. </B
>I upgraded my X server and now I can't type anything into any X application</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>This question should be obsolete.</P
><P
>&#13;Launch the X server via the shortcut under "Cygwin-X" on the start menu. 
</P
><P
>&#13;Technical details: The <B
CLASS="command"
>startxwin.bat</B
> script used to set several enviroment
variables used by the X server to specify the location of files it needs to access.  Specifically 
this batch file would set <CODE
CLASS="parameter"
>XKEYSYMDB</CODE
> to <TT
CLASS="filename"
>/usr/X11R6/lib/X11/XKeysymDB</TT
>.
This file was moved to <TT
CLASS="filename"
>/usr/share/X11/XKeysymDB</TT
>.
The keyboard won't work if <CODE
CLASS="parameter"
>XKEYSYMDB</CODE
> points to a non-existent file.
</P
><P
>&#13;If you are (perhaps unintentionally) using a copy of the old <B
CLASS="command"
>startxwin.bat</B
> (perhaps under another name) to start the X server, remove the environment variables <CODE
CLASS="parameter"
>XAPPLRESDIR</CODE
>, <CODE
CLASS="parameter"
>XCMSDB</CODE
>, <CODE
CLASS="parameter"
>XNLSPATH</CODE
> and <CODE
CLASS="parameter"
>XKEYSYMDB</CODE
> from it, or (preferrably)
use the updated <B
CLASS="command"
>startxwin</B
>.
</P
><P
>&#13;If <B
CLASS="command"
>echo $XKEYSYMDB</B
> outputs something, you have something else setting <CODE
CLASS="parameter"
>XKEYSYMDB</CODE
> in your environment.  Find it and remove it.
</P
><P
>These variables were always being set to the defaults, so they can simply be removed.
See <A
HREF="cygwin-x-faq.html#microsoft-services-for-unix"
>Q: 8.8.</A
> for the reason why you
might need to set them.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-whereis-startxwin-bat"
></A
><B
>3.3. </B
>I can't find <B
CLASS="command"
>startxwin.bat</B
> or <B
CLASS="command"
>startxwin.exe</B
> to start the X server</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
The executable <B
CLASS="command"
>startxwin.exe</B
> previously used to start the X server
has been retired and replaced with a shell script <B
CLASS="command"
>startxwin</B
>.
</P
><P
>&#13;The MS-DOS batch file <B
CLASS="command"
>startxwin.bat</B
> previously used to start the X server
has been retired, as implementing this as a batch file
made it difficult to reliably wait until the the X server had started before
starting any clients.
</P
><P
>&#13;X.Org now uses the prefix <TT
CLASS="filename"
>/usr</TT
> not <TT
CLASS="filename"
>/usr/X11R6</TT
>. So <B
CLASS="command"
>startxwin.bat</B
>
was moved from <TT
CLASS="filename"
>/usr/X11R6/bin/startxwin.bat</TT
> to
<TT
CLASS="filename"
>/usr/bin/startxwin.bat</TT
>.
</P
><P
>&#13;A "XWin Server" shortcut to <B
CLASS="command"
>startxwin</B
> is created on the Start menu, under "Cygwin-X"
</P
><P
>&#13;<B
CLASS="command"
>startxwin</B
> and the Start menu link to it are now installed by the <TT
CLASS="filename"
>xinit</TT
> package.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-moved-1"
></A
><B
>3.4. </B
>Moved question</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-where-are-my-fonts"
></A
><B
>3.5. </B
>My favourite font has gone! The font Emacs uses is just boxes</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Only minimal fonts will be installed after the upgrade from X.Org R6.8 to modular X.Org.
</P
><P
>&#13;Font packages are now named <TT
CLASS="filename"
>font-&lt;author/class&gt;-&lt;fonttype&gt;</TT
>
</P
><P
>&#13;Some packages dependencies have not yet been updated for the fonts they
require, so you may need to manually install the needed fonts.  For example,
to provide the font emacs wants to use by default you will probably want
to install <TT
CLASS="filename"
>font-adobe-dpi75</TT
>
(or <TT
CLASS="filename"
>font-adobe-dpi100</TT
> if you like large fonts).
This package provides the <CODE
CLASS="parameter"
>courier</CODE
>, 
<CODE
CLASS="parameter"
>helvetica</CODE
>,
<CODE
CLASS="parameter"
>new century schoolbook</CODE
>
and <CODE
CLASS="parameter"
>times</CODE
> font families.
</P
><P
>&#13;The <CODE
CLASS="parameter"
>lucida</CODE
> font family is provided by the package
<TT
CLASS="filename"
>font-bh-dpi75</TT
>
(or <TT
CLASS="filename"
>font-bh-dpi100</TT
>).
The monospaced version, <CODE
CLASS="parameter"
>lucida typewriter</CODE
> is provided by the package
<TT
CLASS="filename"
>font-bh-lucidatypewriter-dpi75</TT
>
(or <TT
CLASS="filename"
>font-bh-lucidatypewriter-dpi100</TT
>).
</P
><P
>&#13;Note that after installing fonts you will need to restart the X server or run
<B
CLASS="command"
>xset fp default; xset fp rehash</B
> to make the new fonts available
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-where-is-xxyzy"
></A
><B
>3.6. </B
>Where has <B
CLASS="command"
>xhost</B
>/<B
CLASS="command"
>xlsfonts</B
>/etc. gone?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Previously all the X utility programs were contained in a single package, <TT
CLASS="filename"
>xorg-x11-bin</TT
>, which needed to be updated when any of the programs it contained was updated.  In modular X each of these programs can be found in a separate package, usually named <B
CLASS="command"
>xhost</B
>/<B
CLASS="command"
>xlsfont</B
>/etc.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-how-do-i-get-rid-of-xterm-menu"
></A
><B
>3.7. </B
>How do I get rid of that menu at the top of my xterm?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Run it as <B
CLASS="command"
>xterm +tb</B
>, or add <CODE
CLASS="parameter"
>XTerm*toolBar: false</CODE
> to <TT
CLASS="filename"
>~/.Xresources</TT
></P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-ssh-y"
></A
><B
>3.8. </B
>ssh -X now says "Warning: untrusted X11 forwarding setup failed: xauth key data not generated"</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>See <A
HREF="cygwin-x-faq.html#q-ssh-no-x11forwarding"
>Q: 6.1.</A
> and following.  See <A
HREF="http://cygwin.com/ml/cygwin-xfree/2008-11/msg00154.html"
TARGET="_top"
>point 3 in this mail</A
>.  Use ssh -Y.</P
><P
>&#13;  Technical details: <B
CLASS="command"
>ssh</B
> tried to run <B
CLASS="command"
>xauth
  generate</B
> to create a untrusted cookie for the session, which failed
  because the server isn't compiled with the XCSECURITY extension built-in.
  Since OpenSSH 7.2p1, <B
CLASS="command"
>ssh</B
> does <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>not</I
></SPAN
>
  fallback to trusted forwarding, so no X11 forwarding is setup.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-nedit-wont-start"
></A
><B
>3.9. </B
>
<B
CLASS="command"
>nedit</B
> fails to start with an error message 
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>This question should be obsolete.</P
><P
>&#13;<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>&#13;$ nedit
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  70 (X_PolyFillRectangle)
  Serial number of failed request:  some number
  Current serial number in output stream:  some other number
</PRE
></TD
></TR
></TABLE
>
<B
CLASS="command"
>nedit</B
> needs rebuilding with a patch to work around an issue <TT
CLASS="filename"
>lesstif</TT
>
has with current X servers.
</P
><P
>&#13;Until this happemns, you can work around the issue by adding <CODE
CLASS="parameter"
>XLIB_SKIP_ARGB_VISUALS</CODE
>
to your enviroment, e.g.
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>&#13;$ export XLIB_SKIP_ARGB_VISUALS=1
$ nedit
</PRE
></TD
></TR
></TABLE
>
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-startx-is-has-root-window"
></A
><B
>3.10. </B
>
I start my X server with <B
CLASS="command"
>startx</B
> or <B
CLASS="command"
>xinit</B
> and now all my X windows are contained within one large root Windows window?  How do I get it back to each X window in it's own Windows window?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
This is a deliberate change from Cygwin/X X11 R6.9 behaviour.
</P
><P
>&#13;
<OL
COMPACT="COMPACT"
TYPE="1"
><LI
><P
>&#13;Start the X server using the "XWin Server" shortcut under "Cygwin-X" on the Start menu, or using <B
CLASS="command"
>startxwin</B
>.
</P
><P
>&#13;Note: If you wish to customize the X clients started when the X server starts, 
you can do so using a <TT
CLASS="filename"
>~/.startxwinrc</TT
> script.
</P
></LI
><LI
><P
>Alternatively, add the server option <CODE
CLASS="parameter"
>-multiwindow</CODE
> to your <B
CLASS="command"
>xinit</B
> or <B
CLASS="command"
>startx</B
> invocation, i.e. <B
CLASS="command"
>xinit -- -multiwindow</B
> or <B
CLASS="command"
>startx -- -multiwindow</B
></P
></LI
><LI
><P
>Alternatively, put <B
CLASS="command"
>XWin -multiwindow</B
> into <TT
CLASS="filename"
>~/.xserverrc</TT
> or <TT
CLASS="filename"
>/etc/X11/xinit/xserverrc</TT
></P
></LI
></OL
>

</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-moved-2"
></A
><B
>3.11. </B
>Moved question</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-startxwinrc-exit"
></A
><B
>3.12. </B
>I upgraded and now X exits immediately after starting</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Since <TT
CLASS="filename"
>xinit-1.3.4-1</TT
>, <B
CLASS="command"
>startxwin</B
> is now
implemented by a script based on <B
CLASS="command"
>startx</B
>.  Unfortunately, this
has changed the behaviour in a backwards-incompatible way, as the X server is
now killed when <TT
CLASS="filename"
>~/.startxwinrc</TT
> exits.
</P
><P
>&#13;If you have an empty <TT
CLASS="filename"
>~/.startxwinrc</TT
>, you should change it
to contain <B
CLASS="command"
>exec sleep infinity</B
> so the X server will not exit
until explicitly told to do so.
</P
><P
>&#13;If you are using a custom <TT
CLASS="filename"
>~/.startxwinrc</TT
>, either run the
last client in the foreground (i.e. without <B
CLASS="command"
>&amp;</B
>), so the X
server exits when that client exits, or use <B
CLASS="command"
>exec sleep
infinity</B
> as described above.
</P
><P
>&#13;You should also make sure that <TT
CLASS="filename"
>~/.startxwinrc</TT
> is executable
(e.g. <B
CLASS="command"
>chmod +x ~/.startxwinrc</B
>).
</P
><P
>&#13;See <A
HREF="https://cygwin.com/ml/cygwin-xfree-announce/2014-11/msg00004.html"
TARGET="_top"
>&#13;the announce mail</A
> for more details.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-xserver-nolisten-tcp-default"
></A
><B
>3.13. </B
>I upgraded and now X clients can't connect</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>A1:</P
><P
>&#13;Since X server 1.17, by default the server does not listen for TCP/IP
connections, only accepting local connections on a unix domain socket.
</P
><P
>&#13;For local clients, use <B
CLASS="command"
>DISPLAY=:0.0</B
>, rather than
<B
CLASS="command"
>DISPLAY=localhost:0.0</B
>,
<B
CLASS="command"
>DISPLAY=127.0.0.1:0.0</B
>, <B
CLASS="command"
>DISPLAY=::1:0.0</B
>, etc.
See <A
HREF="cygwin-x-faq.html#display-and-screen"
>Q: 1.6.</A
>.
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>A2:</P
><P
>&#13;For remote clients, rather than connecting over TCP/IP by explicitly setting
<CODE
CLASS="parameter"
>DISPLAY</CODE
> and allowing access using
<B
CLASS="command"
>xhost</B
> or by disabling access control, use ssh tunnelling with
<B
CLASS="command"
>ssh -Y</B
> instead.  (See the User's Guide section <A
HREF="http://x.cygwin.com/docs/ug/using-remote-apps.html#using-remote-apps-ssh"
TARGET="_top"
>on
X forwarding using ssh</A
> for more details).
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>A3:</P
><P
>&#13;Use the <CODE
CLASS="parameter"
>-listen tcp</CODE
> option to restore the previous
behaviour, allowing the X server to open a TCP/IP socket as well
e.g. <B
CLASS="command"
>startxwin -- -listen tcp</B
>.
See <A
HREF="cygwin-x-faq.html#q-command-line-args"
>Q: 4.2.</A
>.
</P
></DIV
></DIV
></DIV
><DIV
CLASS="qandadiv"
><H3
><A
NAME="configuration"
></A
>4. Configuration</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-why-no-xf86config"
></A
><B
>4.1. </B
>Is there an xorg.conf or XF86Config file?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>No.  Options which are configurable are available as command line options.
For example, for more information on configuring other
keyboard layouts using command line options, see <A
HREF="cygwin-x-faq.html#q-non-U.S.-keyboard-layout"
>Q: 5.1.1.</A
></P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-command-line-args"
></A
><B
>4.2. </B
>What are the command line options for <TT
CLASS="filename"
>X</TT
>? How do I add command line options for <TT
CLASS="filename"
>X</TT
>?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>The <A
HREF="http://x.cygwin.com/docs/ug/cygwin-x-ug.html"
TARGET="_top"
>Cygwin/X User's Guide</A
>
and <A
HREF="http://x.cygwin.com/docs/man1/XWin.1.html"
TARGET="_top"
><B
CLASS="command"
>man XWin</B
></A
>
document the command line options for X.</P
><P
>&#13;To supply a command line option to <TT
CLASS="filename"
>X</TT
>:

<UL
COMPACT="COMPACT"
><LI
><P
>&#13;If you use the start menu shortcut to start the X server, you will need to amend it's target to add an option, e.g. <B
CLASS="command"
>C:\cygwin\bin\run.exe --quote /usr/bin/bash.exe -l -c "/usr/bin/startxwin -- -nolock"</B
>
</P
><DIV
CLASS="note"
><BLOCKQUOTE
CLASS="note"
><P
><B
>Note: </B
>Note well that the entire command after <CODE
CLASS="parameter"
>-c</CODE
> is quoted</P
></BLOCKQUOTE
></DIV
><DIV
CLASS="note"
><BLOCKQUOTE
CLASS="note"
><P
><B
>Note: </B
>Note that this start menu shortcut is created by the <TT
CLASS="filename"
>xinit</TT
> package, and your changes will be overwritten when the <TT
CLASS="filename"
>xinit</TT
> package is updated.</P
></BLOCKQUOTE
></DIV
><DIV
CLASS="note"
><BLOCKQUOTE
CLASS="note"
><P
><B
>Note: </B
>Note that X server options to <B
CLASS="command"
>startxwin</B
> are preceded by <CODE
CLASS="parameter"
>--</CODE
>.</P
></BLOCKQUOTE
></DIV
></LI
><LI
><P
>&#13;If you use <B
CLASS="command"
>startxwin</B
>, <B
CLASS="command"
>xinit</B
> or <B
CLASS="command"
>startx</B
> to start the server, run it as e.g. <B
CLASS="command"
>startxwin -- -nolock</B
>,  <B
CLASS="command"
>xinit -- -nolock</B
> or <B
CLASS="command"
>startx -- -nolock</B
>
</P
></LI
><LI
><P
>&#13;If you use <TT
CLASS="filename"
>startxwin.bat</TT
> or <TT
CLASS="filename"
>startxwin.sh</TT
> to start the server, add e.g. <CODE
CLASS="parameter"
>-nolock</CODE
> to the <B
CLASS="command"
>XWin</B
> line in that script.
</P
></LI
></UL
>
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-display-depth-ignored"
></A
><B
>4.3. </B
>Why does <TT
CLASS="filename"
>X</TT
> ignore the display depth that I pass
on the command line?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>When running in windowed mode or GDI-based fullscreen mode,
<TT
CLASS="filename"
>X</TT
> must run the X Server at whatever display depth
Windows is currently using; in these cases the display depth passed on
the command line is ignored.  <TT
CLASS="filename"
>X</TT
> only uses the display
depth parameter when running in a DirectDraw-based fullscreen mode, as
DirectDraw allows applications to change the display resolution and
depth when running in fullscreen mode.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-three-button-emulation"
></A
><B
>4.4. </B
>I have a two button mouse, can I emulate a three button mouse?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Yes.  Pass the <CODE
CLASS="parameter"
>-emulate3buttons <TT
CLASS="replaceable"
><I
>timeout_in_milliseconds</I
></TT
></CODE
>
parameter to <TT
CLASS="filename"
>X</TT
>, where <TT
CLASS="replaceable"
><I
>timeout_in_milliseconds</I
></TT
> is the, optional,
maximum number of milliseconds between a button release and opposite
button press that will trigger an emulated third button press.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="window-auto-focus"
></A
><B
>4.5. </B
>Is there a Focus-Follows-Mouse feature (Auto-Focus)?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>This is a setting of the window manager used. The default window manager
<B
CLASS="command"
>twm</B
> has no such feature. But with <B
CLASS="command"
>fvwm2</B
>
this can be achieved with the this configuration entry:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>Focus FocusFollowsMouse
</PRE
></TD
></TR
></TABLE
>
Other window managers (eg. <B
CLASS="command"
>windowmaker</B
>) have similar features too.</P
><P
>If you are using the <CODE
CLASS="parameter"
>-multiwindow</CODE
> mode you can not set this behaviour
in the window manager but you can use the TweakUI tool to enable this feature
for all windows, not limited to Cygwin/X windows.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="disable-terminate-server"
></A
><B
>4.6. </B
>The option -nounixkill has no effect. How can i prevent the server 
shutdown an Ctrl-Alt-BackSpace?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
This question should be obsolete as the TerminateServer keybinding is
no longer present by default.
</P
><P
>&#13;The TerminateServer keybinding can be enabled with
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>setxkbmap -option terminate:ctrl_alt_bksp</PRE
></TD
></TR
></TABLE
> 
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-multihead"
></A
><B
>4.7. </B
>I have a multihead system. Do I need special options to make it work?
I have a multihead system.  Why are my X-application windows white?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>You should start <TT
CLASS="filename"
>X</TT
> with the <CODE
CLASS="parameter"
>-multiplemonitors</CODE
> option.</P
><P
>Note that this option is enabled by default in <CODE
CLASS="parameter"
>-multiwindow</CODE
> mode.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-firewall"
></A
><B
>4.8. </B
>I have a firewall. Is there anything I have to take care of?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
><TT
CLASS="filename"
>X</TT
> uses port 6000/TCP when the option <CODE
CLASS="parameter"
>-listen
tcp</CODE
> is used. You will have to allow incoming and outgoing traffic on
this port even if you are only using local clients. <TT
CLASS="filename"
>X</TT
> has a builtin access
control so you won't have to worry about opening the port. If you are still
concerned about security, you may limit the allowed hosts to the local IP
addresses.</P
><P
>&#13;If you use a different display number check section
<A
HREF="cygwin-x-faq.html#display-and-screen"
>Q: 1.6.</A
> for details about which ports are
used. For additional information about firewalls and XDMCP connections check
<A
HREF="cygwin-x-faq.html#q-xdmcp-query"
>Q: 7.3.</A
>.
</P
></DIV
></DIV
></DIV
><DIV
CLASS="qandadiv"
><H3
><A
NAME="i18n"
></A
>5. Internationalization</H3
><DIV
CLASS="qandadiv"
><H4
><A
NAME="i18n-keyboard"
></A
>5.1. Keyboard support</H4
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-non-U.S.-keyboard-layout"
></A
><B
>5.1.1. </B
>How do I use a non-U.S. keyboard layout?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Some keyboard layouts are autodetected from the Windows
keyboard settings.  For these layouts no special change is needed.
For all other layouts there is the possibility to configure the layout
via commandline options.</P
><P
>The main option for changing the layout is <CODE
CLASS="parameter"
>-xkblayout
<TT
CLASS="replaceable"
><I
>countrycode</I
></TT
></CODE
> where
<TT
CLASS="replaceable"
><I
>countrycode</I
></TT
> is in most cases the 2
character code which also represents the country in internet adresses
(e.g.  Australia = au, Deutschland = de, France = fr, Japan = jp)</P
><P
>Other options for tweaking the XKB layout are
<CODE
CLASS="parameter"
>-xkbmodel</CODE
>,<CODE
CLASS="parameter"
>-xkbvariant</CODE
>,
<CODE
CLASS="parameter"
>-xkboptions</CODE
> and
<CODE
CLASS="parameter"
>-xkbrules</CODE
>.  These are the counterparts for the
similar named options known from the xorg.conf file.</P
><P
>If the loading fails, check <A
HREF="cygwin-x-faq.html#q-xkb-not-working"
>Q: 5.1.6.</A
></P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-submit-layout"
></A
><B
>5.1.2. </B
>Is there a way to add a layout to the list of autodetected layouts?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>If your keyboard layout is not automatically detected you can send 
the required information for including it into Cygwin/X to cygwin@cygwin.com. 
Please include the following information in your mail:</P
><UL
><LI
><P
>The windows keyboard layout code and the layout name</P
><P
>You will find it in <TT
CLASS="filename"
>/var/log/xwin/XWin.0.log</TT
> in lines similar
to these:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>(--) winConfigKeyboard - Layout: "00001809" (00001809)
(EE) Keyboardlayout "Irish" (00001809) is unknown
</PRE
></TD
></TR
></TABLE
>
</P
></LI
><LI
><P
>The XKB layout code for this layout if you know it.  Please experiment 
with <B
CLASS="command"
>setxkbmap</B
> or  <CODE
CLASS="parameter"
>-xkblayout</CODE
> (as
described in <A
HREF="cygwin-x-faq.html#q-non-U.S.-keyboard-layout"
>Q: 5.1.1.</A
>) to find an XKB layout
code which works for you, otherwise the  maintainers will have to guess it.</P
></LI
><LI
><P
>A description how the layout looks like. This makes it easy to identify
the matching XKB layout code. Many layouts are available from the 
<A
HREF="http://www.microsoft.com/globaldev/reference/keyboards.mspx"
TARGET="_top"
>&#13;Microsoft Global Dev</A
> website
<SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>(It seems that website only works with some browsers)</I
></SPAN
>.
Just add a link to your layout.</P
></LI
></UL
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-modmap-obtaining"
></A
><B
>5.1.3. </B
>Where can I find an xmodmap for my non-U.S. keyboard layout?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>This question should be obsolete
The package <TT
CLASS="filename"
>xkeyboard-config</TT
> should contain just about
any needed layout</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Or, you can use <B
CLASS="command"
>xkeycaps</B
> to automatically
generate a modmap for one of over 208 different layouts.  See the
<A
HREF="http://www.jwz.org/xkeycaps/"
TARGET="_top"
>xkeycaps home page</A
> to download
and for more information.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-how-modmap-and-xdmcp"
></A
><B
>5.1.4. </B
>How do I get my non-U.S. keyboard modmap to be installed when
using xdmcp?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>See <A
HREF="cygwin-x-faq.html#q-non-U.S.-keyboard-layout"
>Q: 5.1.1.</A
></P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-aix-xkb"
></A
><B
>5.1.5. </B
>Logging into AIX via XDMCP causes the keyboard to function as if
<B
CLASS="keycap"
>AltGr</B
> is permanently pressed.</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
[paraphrased from the <A
HREF="http://www.straightrunning.com/XmingNotes/trouble.php"
TARGET="_top"
>Xming FAQ</A
>]
AIX login scripts contain a call to xmodmap (for IBM keyboards) which causes
the keyboard to be incorrectly configured for XWin.
Commenting out those calls should allow you to use XWin with AIX.
</P
><P
>&#13;The XKB extension is now always enabled in the X.Org xserver, so the previous
answer to this question of disabling the XKB extension with the <CODE
CLASS="parameter"
>-kb</CODE
>
parameter is no longer applicable.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-xkb-not-working"
></A
><B
>5.1.6. </B
>Loading an XKB keyboard layout selected with -xkblayout fails</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Not all keyboard layouts are tested very well and some contain
errors or do not work at all. To test if the compiling of your layout
works start

<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>&#13;setxkbmap <TT
CLASS="replaceable"
><I
>de</I
></TT
> -print | xkbcomp -w3 -xkm - :0.0
</PRE
></TD
></TR
></TABLE
>

(replace the "de" with your layout code).  This may produce warnings,
but must not produce errors. If there are errors then please report
them to the mailing list.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="alt-gr-win-xp-powertoys"
></A
><B
>5.1.7. </B
>I have Windows XP with Powertoys installed and AltGr does not work. 
What can I do?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>This question should be obsolete.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="alt-gr-with-old-x"
></A
><B
>5.1.8. </B
>AltGr does not work properly when connecting to various older commercial unices
(e.g. HP-UX, AIX) or to old XFree86.</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
<TT
CLASS="filename"
>xkeyboard-config</TT
> XKB keyboard layouts generally have AltGr
mapped as ISO_Level3_Shift to access additional characters on non-english keyboards.

For reasons unknown to us, this is incompatible with some older X11 releases.
We don't have access to such a machine, so we are unable to track this down and
find a reason.
</P
><P
>&#13;It has been reported that sometimes it helps to run

<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>&#13;DISPLAY=:0.0 setxkbmap <TT
CLASS="replaceable"
><I
>languagecode</I
></TT
>
</PRE
></TD
></TR
></TABLE
>

from a cygwin shell after connecting.</P
><P
>&#13;See this <A
HREF="http://cygwin.com/ml/cygwin-xfree/2011-07/msg00011.html"
TARGET="_top"
>&#13;mailing list thread</A
> for more discussion and a possible workaround.
</P
></DIV
></DIV
></DIV
><DIV
CLASS="qandadiv"
><H4
><A
NAME="i18n-display"
></A
>5.2. Display problems</H4
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-bash-extended-chars"
></A
><B
>5.2.1. </B
>How do I get <B
CLASS="command"
>bash</B
> to display accents and/or
umlauts?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>(Heinz Peter Hippenstiel) Add the following lines to
<TT
CLASS="filename"
>.inputrc</TT
> in your Cygwin home directory
(e.g. <TT
CLASS="filename"
>~/.inputrc</TT
>):
</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>&#13;set input-meta on    # to accept 8-bit characters
set output-meta on   # to show 8-bit characters
set convert-meta off # to show it as character, not the octal representation
</PRE
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-bash-8bit"
></A
><B
>5.2.2. </B
>How do I put <B
CLASS="command"
>bash</B
> into <SPAN
CLASS="QUOTE"
>"8 bit"</SPAN
>
mode?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>See <A
HREF="cygwin-x-faq.html#q-bash-extended-chars"
>Q: 5.2.1.</A
></P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-xterm-utf8"
></A
><B
>5.2.3. </B
>How do I display unicode characters in an <B
CLASS="command"
>xterm</B
>?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>A1: for Cygwin 1.7</P
><P
>&#13;If you have a UTF-8 locale configured, this should all just work :-).
</P
><P
>&#13;To confirm this is working properly, you may try the following:
</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>&#13;$ wget http://www.cl.cam.ac.uk/~mgk25/ucs/examples/quickbrown.txt
[...]
$ cat quickbrown.txt
</PRE
></TD
></TR
></TABLE
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>&#13;$ wget http://www.cl.cam.ac.uk/~mgk25/ucs/examples/UTF-8-demo.txt
[...]
$ cat UTF-8-demo.txt
</PRE
></TD
></TR
></TABLE
><P
>&#13;If you want to be able type unicode characters into this <B
CLASS="command"
>xterm</B
>, you'll need to configure
your <B
CLASS="command"
>bash</B
> shell not to escape 8-bit characters, see <A
HREF="cygwin-x-faq.html#q-bash-extended-chars"
>Q: 5.2.1.</A
>
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>A2: for Cygwin 1.5</P
><P
>&#13;Start your <B
CLASS="command"
>xterm</B
> in UTF-8 mode as <B
CLASS="command"
>xterm +lc -u8</B
>.
</P
><P
>&#13;To confirm this is working properly, you may try the following
</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>&#13;$ wget http://www.cl.cam.ac.uk/~mgk25/ucs/examples/quickbrown.txt
[...]
$ cat quickbrown.txt
</PRE
></TD
></TR
></TABLE
><P
>&#13;For reasons I don't currently understand, the default fixed font is only capable
of supplying accented roman, hiragana and katakana characters, so if you
wish to work with e.g. greek, cyrillic, hebrew, thai, etc. you'll need to
start your xterm specifying a suitable font e.g.
<B
CLASS="command"
>xterm +lc -u8 -fn -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1</B
>
</P
><P
>&#13;To confirm this is working properly, you may try the following
</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>&#13;$ wget http://www.cl.cam.ac.uk/~mgk25/ucs/examples/UTF-8-demo.txt
[...]
$ cat UTF-8-demo.txt
</PRE
></TD
></TR
></TABLE
><P
>&#13;For other programs run from your xterm to output properly (e.g. <B
CLASS="command"
>less</B
>, which is why <B
CLASS="command"
>cat
</B
> is used in the examples above), you may also need to set the LANG environment variable to
<TT
CLASS="replaceable"
><I
>LL_CC</I
></TT
>.UTF-8, where LL_CC is your language and country code.
</P
><P
>&#13;If you want to be able type unicode characters into this <B
CLASS="command"
>xterm</B
>, you'll need to configure
your <B
CLASS="command"
>bash</B
> shell not to escape 8-bit characters, see <A
HREF="cygwin-x-faq.html#q-bash-extended-chars"
>Q: 5.2.1.</A
>
</P
><P
>&#13;See also <A
HREF="http://cygwin.com/faq/faq.html#faq.using.unicode"
TARGET="_top"
>the main Cygwin FAQ question on unicode
support in Cygwin</A
>
</P
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="qandadiv"
><H3
><A
NAME="remote"
></A
>6. Remote connections</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-ssh-no-x11forwarding"
></A
><B
>6.1. </B
>X11Forwarding does not work with OpenSSH under Cygwin</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>A1:</P
><P
>&#13;Try adding the <CODE
CLASS="parameter"
>-v</CODE
> option to <B
CLASS="command"
>ssh</B
>, which often pinpoints the reason for a connection problem.
</P
><P
>&#13;From the <B
CLASS="command"
>ssh</B
> man-page :
<SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>-v Verbose mode.  Causes ssh to print debugging messages about its progress.
This is helpful in debugging connection, authentication, and configuration problems.
Multiple -v options increase the verbosity.  The maximum is 3.</I
></SPAN
>
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>A2:</P
><P
>Before establishing the ssh connection the xserver must be
started and the environment variable <CODE
CLASS="parameter"
>DISPLAY</CODE
>
must be set.

<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>&#13;$ DISPLAY=<TT
CLASS="replaceable"
><I
>:0.0</I
></TT
>
$ export DISPLAY
$ ssh -Y <TT
CLASS="replaceable"
><I
>remotehost</I
></TT
>
</PRE
></TD
></TR
></TABLE
>

or

<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>&#13;$ DISPLAY=<TT
CLASS="replaceable"
><I
>:0.0</I
></TT
> ssh -Y <TT
CLASS="replaceable"
><I
>remotehost</I
></TT
>
</PRE
></TD
></TR
></TABLE
>
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>A3:</P
><P
>&#13;Make sure you're not starting <B
CLASS="command"
>ssh</B
> with the option
<CODE
CLASS="parameter"
>-X</CODE
>.  Since OpenSSH 7.2p1, <B
CLASS="command"
>ssh</B
> does
<SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>not</I
></SPAN
> fallback to trusted forwarding, option <CODE
CLASS="parameter"
>&#13;-Y</CODE
>, so no X11 forwarding is setup.  Use <B
CLASS="command"
>ssh -Y</B
>.
</P
><P
>&#13;Make sure you're not starting <B
CLASS="command"
>ssh</B
> with the option <CODE
CLASS="parameter"
>-x</CODE
>
(lowercase). This disables X11 forwarding.
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>A4:</P
><P
>Check that X11Forwarding is not disabled in the ssh client
configuration.</P
><P
>The configfiles are by default
<TT
CLASS="filename"
>~/.ssh/config</TT
> and
<TT
CLASS="filename"
>/etc/ssh_config</TT
>.  The file in the home directory
overrides settings in the global one.</P
><P
>The configfile is split into various sections starting with
<SPAN
CLASS="QUOTE"
>"Host <TT
CLASS="replaceable"
><I
>wildcard</I
></TT
>"</SPAN
>.  The section
applies to all hosts where <TT
CLASS="replaceable"
><I
>wildcard</I
></TT
> matches
the hostname.</P
><P
>If this section contains an entry <SPAN
CLASS="QUOTE"
>"ForwardX11 no"</SPAN
>
then X11Forwarding is disabled. To enable it change the entry to:
</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>&#13;ForwardX11 yes
</PRE
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>A5:</P
><P
>Check that X11Forwarding is not disabled in the ssh server
configuration.</P
><P
>The configfile is by default
<TT
CLASS="filename"
>/etc/ssh/sshd_config</TT
>.  If there is an entry
<SPAN
CLASS="QUOTE"
>"X11Forwarding no"</SPAN
> then X11Forwarding is
disabled. </P
><P
>If you have write access to the config file then change it to

<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>&#13;X11Forwarding yes
</PRE
></TD
></TR
></TABLE
>

The OpenSSH server must be restarted or SIGHUP'ed to re-read the configuration
file after it is changed.

Otherwise, ask your administrator to change this for you.</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>A6:</P
><P
>&#13;[Frederick W. Wheeler]
If the <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>remote</I
></SPAN
> machine is a Windows machine using Cygwin OpenSSH server,
make sure the Cygwin <B
CLASS="command"
>xauth</B
> package is installed on the <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>remote</I
></SPAN
>
machine.  The OpenSSH server needs to be able to run <B
CLASS="command"
>xauth</B
> to do X11 Forwarding.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-bad-atom"
></A
><B
>6.2. </B
>Why do remote programs crash with an <SPAN
CLASS="errorname"
>X Error of failed request: BadAtom</SPAN
>?
Why do remote programs exit when you try to copy and paste?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>This question should be obsolete since the SECURITY extension
is now disabled</P
><P
>OpenSSH 3.8 enables untrusted <A
HREF="glossary.html#gloss-x11forwarding"
><I
CLASS="glossterm"
>X11Forwarding</I
></A
> by default when
connecting to an ssh server that supports it.</P
><P
> You will
quickly notice that this is the case if most of your X applications
are now killed when you try to copy and paste, X applications fail
with an error similar to that below,  or if
<B
CLASS="command"
>xdpyinfo</B
> returns only a fraction of the supported
extensions that it does if run locally.</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
> X Error of failed request: BadAtom (invalid Atom parameter)
  Major opcode of failed request: 18 (X_ChangeProperty)
  Atom id in failed request: 0x114
  Serial number of failed request: 370
  Current serial number in output stream: 372
</PRE
></TD
></TR
></TABLE
><P
>It is easiest to just override untrusted X11Forwarding by passing
<CODE
CLASS="parameter"
>-Y</CODE
> to <B
CLASS="command"
>ssh</B
> in place of
<CODE
CLASS="parameter"
>-X</CODE
>.  The <CODE
CLASS="parameter"
>-Y</CODE
> does the
same thing as <CODE
CLASS="parameter"
>-X</CODE
>, but it enables trusted X11 forwarding
for the current connection.</P
><P
>Setting
<SPAN
CLASS="QUOTE"
>"ForwardX11Trusted yes"</SPAN
> in the ssh client configuration file
does the same thing. See <B
CLASS="command"
>man ssh_config</B
> for more information.
</P
><P
>&#13;See also <A
HREF="cygwin-x-faq.html#q-ssh-no-x11forwarding"
>Q: 6.1.</A
>
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-trusted-untrusted-x11-forwarding"
></A
><B
>6.3. </B
>I'm confused about the difference between trusted and untrusted X11 forwarding.
What does "Warning: untrusted X11 forwarding setup failed: xauth key data not generated" mean?
Why is the SECURITY extension disabled?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
The warning means that ssh is going to use <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>trusted</I
></SPAN
> X11 forwarding
because <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>untrusted</I
></SPAN
> X11 forwarding depends on the SECURITY extension,
which isn't built into the X server and has been disabled by default upstream.
</P
><P
>&#13;Trusted X11 forwarding means that you trust the server that you wish to
ssh into.
The X server will allow remote clients to do whatever a local client would
be able to do to your X session, for example, monitor your keypresses and
take a screenshot.
Such programs could be run by a malicious or compromised root user on
the ssh server, or under your account if it was compromised on the ssh server.
</P
><P
>&#13;Starting with OpenSSH 3.8, untrusted forwarding is the default when X forwarding
is requested using the <CODE
CLASS="parameter"
>-X</CODE
> command line option and you need
to use the option <CODE
CLASS="parameter"
>-Y</CODE
> or specify
<SPAN
CLASS="QUOTE"
>"ForwardX11Trusted yes"</SPAN
> in the client configuration for trusted forwarding
by default.
</P
><P
>&#13;Since OpenSSH 7.2p1, untrusted forwarding (<B
CLASS="command"
>ssh</B
>
<CODE
CLASS="parameter"
>-X</CODE
>) does <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>not</I
></SPAN
> fallback to
<B
CLASS="command"
>ssh</B
> <CODE
CLASS="parameter"
>-Y</CODE
> trusted forwarding.</P
><P
>&#13;So why is this disabled?
Untrusted X11 forwarding was meant to be a way to allow logins to
unknown or insecure systems.  It generates a cookie with xauth and uses
the security extension to limit what the remote client is allowed to do.
But this is widely considered to be not useful, because the security
extension uses an arbitrary and limited access control policy, which
results in a lot of applications not working correctly (e.g. not being
able to cut and paste) and what is really a false sense of security.
See this mail <A
HREF="http://cygwin.com/ml/cygwin-xfree/2008-11/msg00154.html"
TARGET="_top"
>for more on the subject</A
>.
</P
><P
>&#13;(Words adapted from an email by Yaakov Selkowitz)
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-warning-no-xauth-data"
></A
><B
>6.4. </B
>
What does "Warning: no xauth data; using fake authentication data for X11 forwarding" mean?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Unless you started the X server with the <CODE
CLASS="parameter"
>-auth</CODE
> option
(typically by using <B
CLASS="command"
>startx</B
>) this warning is expected and
can safely be ignored.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-twenty-minute-timeout"
></A
><B
>6.5. </B
>
Why can't new remote X clients connect to the X server after 20 minutes?
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Starting with OpenSSH 5.6, ssh enforces the ForwardX11Timeout (which defaults
to 1200 seconds) when an untrusted connections is requested, even if an untrusted
connection could not be made (e.g. you used <B
CLASS="command"
>ssh -X</B
> which asks for
an untrusted connection, and got the "untrusted X11 forwarding setup failed" warning).
This means that no new connections to the X server
can be made 20 minutes after the ssh connection is established.
</P
><P
>&#13;Use <B
CLASS="command"
>ssh -Y</B
>.  See also <A
HREF="cygwin-x-faq.html#q-bad-atom"
>Q: 6.2.</A
>.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-remote-clients-cant-connect"
></A
><B
>6.6. </B
>
Remote clients can't connect
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
The X server now uses <CODE
CLASS="parameter"
>-nolisten tcp</CODE
> by default, which increases
the security of the X server by not opening a TCP/IP socket.
</P
><P
>&#13;Use the <CODE
CLASS="parameter"
>-listen tcp</CODE
> option to allow the X server to open
a TCP/IP socket as well, e.g. <B
CLASS="command"
>startxwin -- -listen tcp</B
>.
See <A
HREF="cygwin-x-faq.html#q-command-line-args"
>Q: 4.2.</A
>.
</P
><P
>&#13;A better solution is to stop explicitly setting DISPLAY and allowing access using
<B
CLASS="command"
>xhost</B
> or by disabling access control.
Use <B
CLASS="command"
>ssh -Y</B
> instead.  (See the User's Guide section <A
HREF="http://x.cygwin.com/docs/ug/using-remote-apps.html#using-remote-apps-ssh"
TARGET="_top"
>on
X forwarding using ssh</A
> for more details).
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-local-noncygwin-clients-cant-connect"
></A
><B
>6.7. </B
>
X sessions forwarded by <B
CLASS="command"
>PuTTY</B
> can't connect.
Non-cygwin local X clients can't connect.
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
The X server now uses <CODE
CLASS="parameter"
>-nolisten tcp</CODE
> by default, which increases
the security of the X server by not opening a TCP/IP socket, only a local (UNIX
domain) socket.  Non-cygwin applications cannot connect to that socket.
</P
><P
>&#13;Use the <CODE
CLASS="parameter"
>-listen tcp</CODE
> option to allow the X server to open
a TCP/IP socket as well, e.g. <B
CLASS="command"
>startxwin -- -listen tcp</B
>.
See <A
HREF="cygwin-x-faq.html#q-command-line-args"
>Q: 4.2.</A
>.
</P
></DIV
></DIV
></DIV
><DIV
CLASS="qandadiv"
><H3
><A
NAME="xdmcp"
></A
>7. XDMCP connections</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-xdmcp-no-valid-address"
></A
><B
>7.1. </B
><SPAN
CLASS="errorname"
>XDMCP fatal error: Session declined No valid
address</SPAN
></P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Cygwin/X is sometimes unable to determine which local network
interface's address should be reported to the <A
HREF="glossary.html#gloss-xdmcp"
><I
CLASS="glossterm"
>XDMCP</I
></A
> server; in these 
cases you need to pass <CODE
CLASS="parameter"
>-from</CODE
> <TT
CLASS="replaceable"
><I
>local_host_name_or_ip_address</I
></TT
> to
<TT
CLASS="filename"
>X</TT
> to specify which interface address to report.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-audit-client-rejected"
></A
><B
>7.2. </B
>Why does Cygwin/X report AUDIT: client 1 rejected from IP 
<TT
CLASS="replaceable"
><I
>remotehost</I
></TT
>?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>The problem is most likely a wrong DNS (Network name resolution). Make 
sure your windows host has a hostname which is valid from linux too and an IP 
address which linux can resolve to that hostname.</P
><P
>If you add a line
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>&#13;192.168.26.1 myhost
</PRE
></TD
></TR
></TABLE
>
to /etc/hosts on the <A
HREF="glossary.html#gloss-xdmcp"
><I
CLASS="glossterm"
>XDMCP</I
></A
> server with the IP address and the hostname 
of your windows host the name resolution should work.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-xdmcp-query"
></A
><B
>7.3. </B
>I get no login screen when using <CODE
CLASS="parameter"
>-query</CODE
></P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>A1: Disabled XDMCP on servers</P
><P
>[Mika Laitio] For security reasons, <A
HREF="glossary.html#gloss-xdmcp"
><I
CLASS="glossterm"
>XDMCP</I
></A
> is not enabled by
default on most Linux/UNIX/*NIX/*BSD distributions (Red Hat, Mandrake,
SuSE, FreeBSD, NetBSD, etc.) by default.  You have to manually enable
remote logins to your X Display Manager (e.g. <B
CLASS="command"
>xdm</B
>,
<B
CLASS="command"
>kdm</B
>, or <B
CLASS="command"
>gdm</B
>).  The location of
the proper config file is distribution/OS dependent, but a short list of
known config file locations is given in <A
HREF="cygwin-x-faq.html#tbl-config-files"
>Table 1</A
>.  You must change the line:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>&#13;[Xdmcp]
Enable=false
</PRE
></TD
></TR
></TABLE
>
to:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>&#13;[Xdmcp]
Enable=true
</PRE
></TD
></TR
></TABLE
>
or for xdm style configuration:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>&#13;DisplayManager.requestPort:     0
</PRE
></TD
></TR
></TABLE
>
to:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>&#13;!DisplayManager.requestPort:     0
</PRE
></TD
></TR
></TABLE
>
</P
><DIV
CLASS="table"
><A
NAME="tbl-config-files"
></A
><P
><B
>Table 1. Known XDM Configuration File Locations</B
></P
><TABLE
BORDER="1"
FRAME="border"
CLASS="CALSTABLE"
><COL/><COL/><COL/><COL/><THEAD
><TR
><TH
>Distribution/OS</TH
><TH
>Version</TH
><TH
>Display Manager</TH
><TH
>Location</TH
></TR
></THEAD
><TBODY
VALIGN="top"
><TR
><TD
>Linux Mandrake</TD
><TD
>8.1</TD
><TD
>kdm</TD
><TD
>/usr/share/config/kdm/kdmrc</TD
></TR
><TR
><TD
>Debian GNU/Linux</TD
><TD
>Unstable</TD
><TD
>kdm</TD
><TD
>/etc/kde3/kdm/kdmrc</TD
></TR
><TR
><TD
>Debian GNU/Linux</TD
><TD
>Unstable</TD
><TD
>gdm</TD
><TD
>/etc/X11/gdm/gdm.conf</TD
></TR
><TR
><TD
>Debian GNU/Linux</TD
><TD
>Unstable</TD
><TD
>xdm</TD
><TD
>/etc/X11/xdm/xdm-config</TD
></TR
><TR
><TD
>Debian GNU/Linux</TD
><TD
>Unstable</TD
><TD
>wdm</TD
><TD
>/etc/X11/wdm/wdm-config</TD
></TR
></TBODY
></TABLE
></DIV
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>A2: XDMCP and firewalls</P
><P
><A
HREF="glossary.html#gloss-xdmcp"
><I
CLASS="glossterm"
>XDMCP</I
></A
> will not work correctly if you have a personal firewall installed
or the built-in firewall of Windows is activated.</P
><P
>The XDMCP protocol will send and receive data on port 177/UDP. But the 
actual connections will be made to the local port 6000/TCP. It is safe to 
allow connections since the xserver has an own security layer. An overview 
of used ports is given in <A
HREF="cygwin-x-faq.html#tbl-xdmcp-ports"
>Table 2</A
>.
</P
><DIV
CLASS="table"
><A
NAME="tbl-xdmcp-ports"
></A
><P
><B
>Table 2. Ports used with XDMCP connections</B
></P
><TABLE
BORDER="1"
FRAME="border"
CLASS="CALSTABLE"
><COL/><COL/><COL/><COL/><THEAD
><TR
><TH
>Port</TH
><TH
>Protocol</TH
><TH
>Direction</TH
><TH
>Comment</TH
></TR
></THEAD
><TBODY
VALIGN="top"
><TR
><TD
>177</TD
><TD
>UDP</TD
><TD
>Incoming/Outgoing</TD
><TD
>Actual XDMCP connection</TD
></TR
><TR
><TD
>6000+<CODE
CLASS="parameter"
>display</CODE
></TD
><TD
>TCP</TD
><TD
>Incoming</TD
><TD
>Connection for X11 clients. <CODE
CLASS="parameter"
>display</CODE
> is 
usually 0 except if you specify it on the commandline.</TD
></TR
></TBODY
></TABLE
></DIV
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-mandrake-8.1-xdmcp"
></A
><B
>7.4. </B
>XDMCP does not work with Mandrake 8.1</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>See <A
HREF="cygwin-x-faq.html#q-xdmcp-query"
>Q: 7.3.</A
></P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-xdmcp-gdm"
></A
><B
>7.5. </B
>Why does GDM not work with <CODE
CLASS="parameter"
>-clipboard</CODE
></P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Newer versions of GDM have a more complex startup mechanism than the other
display manager have. This can interfere with the way the clipboard integration
client is started.
</P
><P
>&#13;Workaround: add (or modify) this section in the <TT
CLASS="filename"
>gdm.conf</TT
> 
(or <TT
CLASS="filename"
>/etc/gdm/custom.conf</TT
>) file.
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>&#13;[daemon]
KillInitClients=false
</PRE
></TD
></TR
></TABLE
>
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-solaris-fonts"
></A
><B
>7.6. </B
>I get no login screen for Solaris</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>See also <A
HREF="cygwin-x-faq.html#q-remote-solaris"
>Q: 7.7.</A
> and 
<A
HREF="cygwin-x-faq.html#q-cde-via-xdmcp-hangs"
>Q: 7.8.</A
></P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>[David Dawson] For whatever reason, certain versions of Solaris
need fonts that are not provided by Cygwin/X; the result is that you
may see the Solaris background tile and the hourglass cursor, but the
XDM login prompt will never appear.  The simplest solution is to point
Cygwin/X at the font server that is usually running on the Solaris
machine.  You'll need a command line similar to the following to start
your <A
HREF="glossary.html#gloss-xdmcp"
><I
CLASS="glossterm"
>XDMCP</I
></A
> session and to connect to the Solaris font server:</P
><P
>&#13;<KBD
CLASS="userinput"
>X -query
<TT
CLASS="replaceable"
><I
>solaris_hostname_or_ip_address</I
></TT
> -fp
tcp/<TT
CLASS="replaceable"
><I
>solaris_hostname_or_ip_address</I
></TT
>:7100</KBD
>
</P
><DIV
CLASS="note"
><BLOCKQUOTE
CLASS="note"
><P
><B
>Note: </B
>The <CODE
CLASS="parameter"
>-fp</CODE
> parameter is a general X Server
parameter, it is not specific to Cygwin/X; therefore, the
<CODE
CLASS="parameter"
>-fp</CODE
> is documented in the <A
HREF="http://x.cygwin.com/docs/man1/Xserver.1.html"
TARGET="_top"
>X Server manual page</A
>.  For
additional information about fonts, see <A
HREF="http://www.x.org/archive/X11R7.5/doc/fonts/fonts.html"
TARGET="_top"
>Fonts in X11R6.7</A
>.</P
></BLOCKQUOTE
></DIV
><P
>The standard port number for a font server is
<TT
CLASS="literal"
>7100</TT
>, however, you may need to ask your system
administrator what the font server port number is if you cannot
connect to a font server on port <TT
CLASS="literal"
>7100</TT
>.  It is also
possible that your Solaris machine is not running a font server, in
which case you will need to consult your Solaris documentation for
instructions on how to run a font server.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-remote-solaris"
></A
><B
>7.7. </B
>XDMCP freezes with remote Solaris machine!</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>See also <A
HREF="cygwin-x-faq.html#q-solaris-fonts"
>Q: 7.6.</A
> and 
<A
HREF="cygwin-x-faq.html#q-cde-via-xdmcp-hangs"
>Q: 7.8.</A
></P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Solaris appears to not support certain display bit depths, such
as 24 bits per pixel.  Change your Windows display bit depth to 8,
16, or 32 and try logging in again.  File a complaint with Sun if this
issue is important to you, or change your Solaris machines to use
XFree86 instead of the Solaris X Window System.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-cde-via-xdmcp-hangs"
></A
><B
>7.8. </B
>Login to <ACRONYM
CLASS="acronym"
>CDE</ACRONYM
> on Solaris via XDMCP hangs
Cygwin/X.</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>See also <A
HREF="cygwin-x-faq.html#q-solaris-fonts"
>Q: 7.6.</A
> and <A
HREF="cygwin-x-faq.html#q-remote-solaris"
>Q: 7.7.</A
></P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Install the <A
HREF="http://www.sun.com/bigadmin/patches/indexRec.html"
TARGET="_top"
>recommended
set of patches</A
> for your version of Solaris.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-xdmcp-info"
></A
><B
>7.9. </B
>Where can I find more information about XDMCP.</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>See the <A
HREF="http://en.tldp.org/HOWTO/XDMCP-HOWTO/"
TARGET="_top"
>Linux XDMCP HOWTO</A
> for more
information about XDMCP.</P
></DIV
></DIV
></DIV
><DIV
CLASS="qandadiv"
><H3
><A
NAME="troubleshooting"
></A
>8. Troubleshooting</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-fatal-error"
></A
><B
>8.1. </B
>Cygwin/X failed with "Fatal Error". What does this mean?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>The Fatal Error is a general error message. More specific information
what caused this is available in <TT
CLASS="filename"
>/var/log/xwin/XWin.0.log</TT
>. Please
check the common error messages in <A
HREF="cygwin-x-faq.html#errors"
>the Section called  
<SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>Error and Warning Messages</I
></SPAN
></A
>. If your error is not mentioned 
proceed with <A
HREF="cygwin-x-faq.html#q-error-message-not-listed"
>Q: 8.4.</A
></P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-log-file-location"
></A
><B
>8.2. </B
>Is there a log file that I can look at for diagnostic
information and error messages?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Yes.  The Cygwin/X log file is located at
<TT
CLASS="filename"
>/var/log/xwin/XWin.0.log</TT
>.  You will find solutions to the most
common error messages in <A
HREF="cygwin-x-faq.html#errors"
>the Section called
<SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>Error and Warning Messages</I
></SPAN
></A
>.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-error-message-interpretation"
></A
><B
>8.3. </B
>I have a specific error message, what does it mean?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>See the Error and Warning Messages section for help with specific error
messages.  Return to this section if you do not find a specific answer
for the error message that you have.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-error-message-not-listed"
></A
><B
>8.4. </B
>I have a specific error message that is not addressed in the
Error and Warning Messages section.</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Search the <A
HREF="http://cygwin.com/ml/cygwin/"
TARGET="_top"
>Cygwin/X
mailing list archives</A
> to see if the error message has already
been reported and/or addressed.  Report the error message to the
cygwin@cygwin.com mailing list, how the
error message was caused, and the behavior of the X Server after the
error message was generated (exit, freeze, etc.), only if the error
message has not been reported, if the circumstances that produced the
error message are significantly different from other reports, or if
you have additional information regarding the error message to
contribute. Please include <TT
CLASS="filename"
>/var/log/xwin/XWin.0.log</TT
> in your mail.
This may help us identify the cause of your problem quicker.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-but-report-ignored"
></A
><B
>8.5. </B
>My bug report the Cygwin/X mailing list was ignored.  What do I
do now?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Some bug reports are deliberately ignored by project members if
the bug in question was recently dealt with; did you <A
HREF="http://cygwin.com/ml/cygwin/"
TARGET="_top"
>search the mailing list archives</A
>
for a solution to your problem before submitting your bug report?
Some bug reports are ignored if they do not contain sufficient
information to understand the situation that produces the bug; did
your bug report have enough information?  Some bug reports are missed
or forgotten, thus some valid bug reports do not receive a reply;
simply resubmit such bug reports that have not received a response
within 7 days of submission.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="freeze-at-startup"
></A
><B
>8.6. </B
>Why does Cygwin/X freeze right after startup?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Zone Alarm 5 is known to break Cygwin/X. As a result you'll see
this line (or a similar) as last output in <TT
CLASS="filename"
>/var/log/xwin/XWin.0.log</TT
>
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>Rules = "xorg" Model = "pc101" Layout = "us" Variant = "(null)" Options = "(null)"</PRE
></TD
></TR
></TABLE
>
Disabling Zone Alarm will not solve this problem. You can only uninstall Zone Alarm 5 and switch to an earlier version (4.5 is known to work) or use a different
personal firewall.
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Another reason is <TT
CLASS="filename"
>/tmp</TT
> mounted in textmode. This does
only happen with the <CODE
CLASS="parameter"
>-multiwindow</CODE
> and 
<CODE
CLASS="parameter"
>-clipboard</CODE
> switches because of the extra threads within
Cygwin/X. 
</P
><P
>You can remount <TT
CLASS="filename"
>/tmp</TT
> to binmode with these commands:
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>mount -b "$(cygpath -m /tmp)" /tmp
</PRE
></TD
></TR
></TABLE
>

If this fails with an error message stating insufficient rights, try

<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>mount -b -u "$(cygpath -m /tmp)" /tmp
</PRE
></TD
></TR
></TABLE
>
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="poor-performance"
></A
><B
>8.7. </B
>Cygwin/X has very poor performance. What's the reason?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Most likely you have installed some kind of personal firewall, VPN 
software or any other software that modifies the TCP/IP stack of Windows.
Especially Webwasher and some other filtering software are known to slow
down the network traffic.</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Some online virus scanners like Symantec Antivirus do slowdown Cygwin/X
a lot. They scan every file access and network traffic which causes serious 
processing overhead beyond that from the X11 protocol and the unix emulation
layer.</P
><P
>So far there is no known solution but to disable the virus scanner
completely.</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>[Dr. Edward Wornar] Certain programs that are installed by various 
drivers and software packages can consume an incredible amount of system
resources and processing time.  One known example of such a program is
<TT
CLASS="filename"
>ATI2evxx.exe</TT
>, a utility installed with some ATI
Technologies graphics card drivers.  <A
HREF="http://www.answersthatwork.com/"
TARGET="_top"
>Answers That Work</A
> has information on
<TT
CLASS="filename"
>ATI2evxx.exe</TT
> on their <A
HREF="http://www.answersthatwork.com/Tasklist_pages/tasklist_a.htm"
TARGET="_top"
>Task List Programs - A</A
> page.  You
may want to try disabling, one-by-one,
<TT
CLASS="filename"
>ATI2evxx.exe</TT
> and other such programs until you
find the program that is causing the slowdown.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="microsoft-services-for-unix"
></A
><B
>8.8. </B
>I have Microsoft Services for Unix installed and can't type anything. 
Help me!!!</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Microsoft Services for Unix set some environment variables which 
points Cygwin/X to outdated or not existing files. These variables are
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>XAPPLRESDIR
XCMSDB
XKEYSYMDB
XNLSPATH
</PRE
></TD
></TR
></TABLE
>
To have Cygwin/X work correctly you have to unset at least <CODE
CLASS="parameter"
>&#13;XKEYSYMDB</CODE
>. 
</P
><P
>&#13;Reported by Juan Medina, Pavel Rozenboim
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-tasklist-programs-slow"
></A
><B
>8.9. </B
>Cygwin/X is extremely slow, especially when using XDMCP to
connect to remote machines.</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>see <A
HREF="cygwin-x-faq.html#poor-performance"
>Q: 8.7.</A
>.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-trackpoint"
></A
><B
>8.10. </B
>Simulated mouse wheel scrolling doesn't work with a TrackPoint mouse
(found on IBM laptops) or Synaptics Touchpads</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>[Gerald S. Williams] The TrackPoint driver tries to send scroll
up/down messages to the default scrollbar in a window.  Cygwin/X does
not use Windows scrollbars for X Client windows, so we must configure
the TrackPoint driver to send standard WM_MOUSEWHEEL messages to the
Cygwin/X window.  This can be done by editing the TrackPoint
configuration that can be found in the
<TT
CLASS="filename"
>tp4table.dat</TT
> and/or
<TT
CLASS="filename"
>tp4scrol.dat</TT
> files, which are usually located in
<TT
CLASS="filename"
>%SYSTEM_ROOT%\System32\</TT
>,
<TT
CLASS="filename"
>%PROGRAMFILES%\Synaptics\SynTP\</TT
> or
<TT
CLASS="filename"
>%PROGRAMFILES%\Lenovo\Trackpoint\</TT
>.
</P
><P
>&#13;Add the following to the <SPAN
CLASS="QUOTE"
>"Pass 0 rules"</SPAN
>section and then
restart your computer to ensure the driver reloads it's settings.
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>&#13;; X Windows
*,*,XWin.exe,*,*,*,WheelStd,0,9
</PRE
></TD
></TR
></TABLE
>
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="no-rootwindow-with-run"
></A
><B
>8.11. </B
>Why is the root window not shown in normal mode?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>This question should be obsolete.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="cross-as-pointer"
></A
><B
>8.12. </B
>Why is the cross the default cursor in multiwindow mode?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>This question should be obsolete</P
><P
>To workaround this add the command <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>run xsetroot -cursor_name left_ptr -fg white -bg black</PRE
></TD
></TR
></TABLE
> to <TT
CLASS="filename"
>startxwin.bat</TT
></P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="xterm-not-resizing"
></A
><B
>8.13. </B
>How can I adjust the linewidth in bash after resizing XTerm?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>We think this question is probably obsolete</P
><P
>Try starting <TT
CLASS="filename"
>resize</TT
>.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="numlock-modifier"
></A
><B
>8.14. </B
>Why do some menus not work if Num-Lock is on?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>The problem are programs which treat Num-Lock as modifier similar to Control. The programs expect a plain click but received some strange Num-Lock-Click combination and can't associate this with the action "open menu".</P
></DIV
></DIV
></DIV
><DIV
CLASS="qandadiv"
><H3
><A
NAME="errors"
></A
>9. Error and Warning Messages</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-owner-tmp-.X11-unix"
></A
><B
>9.1. </B
><SPAN
CLASS="errorname"
>_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root</SPAN
></P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>&#13;_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created
</PRE
></TD
></TR
></TABLE
>
</P
><P
>This question should be obsolete as this error is no longer generated.</P
><P
>This warning message can be ignored; it does not cause any known
problems.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-error-security-policy"
></A
><B
>9.2. </B
><SPAN
CLASS="errorname"
>error opening security policy file
/usr/X11R6/lib/X11/xserver/SecurityPolicy</SPAN
></P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>This question should be obsolete as this error is no longer generated.</P
><P
>This error is harmless.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="duplicate-invocation"
></A
><B
>9.3. </B
>Duplicate invocation on display number: 0.  Exiting.</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Most likely you have started <TT
CLASS="filename"
>X</TT
> twice.</P
><P
>if you start multiple instances of <TT
CLASS="filename"
>X</TT
> you have to
give then unique display numbers
</P
><P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>X -query foo
X :1 -query bar
X :2 -query blubb
</PRE
></TD
></TR
></TABLE
>
Specifying no display number is the same as using <CODE
CLASS="parameter"
>:0</CODE
></P
><P
>If you want another terminal window (which in fact is just a convenient side effect of running <TT
CLASS="filename"
>startxwin</TT
>) you should do this by starting <TT
CLASS="filename"
>xterm &amp;</TT
> from an existing terminal window, from the notification area icon menu, from a cygwin shell or from the start menu.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-error-font-eof"
></A
><B
>9.4. </B
><SPAN
CLASS="errorname"
>Fatal server error: could not open default font
'fixed'</SPAN
></P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>This question should be obsolete as the default font is now built into the server.</P
><P
>This error occurs for one of three reasons:</P
><OL
COMPACT="COMPACT"
TYPE="1"
><LI
><P
>You do not have a font package which provides the default font
('fixed') installed.  This is
rarely the problem; but in the event that it is the problem, just
rerun Cygwin' setup program, select the
font-misc-misc package and install it.</P
></LI
><LI
><P
>The mount point for
<TT
CLASS="filename"
>/usr/share/fonts/</TT
> was either invalid (does 
not point to a valid folder on your system) or is a text-mode mount.
You can confirm that this is the problem by running <B
CLASS="command"
>mount</B
> 
from a Cygwin shell and checking the disk path returned for the
<TT
CLASS="filename"
>/usr/share/fonts/</TT
> mount point.</P
><DIV
CLASS="note"
><BLOCKQUOTE
CLASS="note"
><P
><B
>Note: </B
>You cannot reliably fix this problem by deleting your
Cygwin installation and reinstalling it.  The mount points that
Cygwin was using will be left in your system settings and the
invalid mount point for
<TT
CLASS="filename"
>/usr/share/fonts/</TT
> will be used
again when you perform the reinstallation.  You SHOULD follow the
instructions below to fix the problem.</P
></BLOCKQUOTE
></DIV
><P
>To fix the problem, perform the following steps:</P
><OL
COMPACT="COMPACT"
TYPE="a"
><LI
><P
>Open a Cygwin shell and run <B
CLASS="command"
>umount
/usr/share/fonts/</B
>.</P
></LI
><LI
><P
>Close the Cygwin shell.</P
></LI
><LI
><P
>Run Cygwin's setup program.</P
></LI
><LI
><P
>For each of the font packages, if they are marked Keep,
then select Reinstall, otherwise leave them as they are:</P
></LI
><LI
><P
>Allow Cygwin's setup program to download and
reinstall the fonts packages.  The key to fixing this problem is that
the files were previously untarred into an invalid location; removing
the mount point for the fonts directory should result in the files
being untarred to a valid location.</P
></LI
></OL
></LI
><LI
><P
>You chose "DOS/text" as the "Default Text File type" during Cygwin setup, ignoring the advice that the Default Text File Type should be left on Unix/binary unless you have a very good reason to switch it to DOS/text.</P
><P
>Open a Cygwin shell and run.</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>&#13;umount /usr/share/fonts/
mount -f -s -b "C:/cygwin/usr/share/fonts" "/usr/share/fonts"
</PRE
></TD
></TR
></TABLE
><P
>Reinstall your fonts</P
></LI
></OL
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-removing-font-path-element"
></A
><B
>9.5. </B
><SPAN
CLASS="errorname"
>Could not init font path element
/usr/share/fonts/<TT
CLASS="replaceable"
><I
>*</I
></TT
>/, removing from
list!</SPAN
></P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>These warnings are generally harmless since they indicate that
default search paths for fonts do not actually contain fonts; this is
only a problem if the <TT
CLASS="filename"
>misc</TT
> path does not contain
fonts and/or all of the paths do not contain fonts.</P
><P
>If you are getting these message and the X Server is also
failing to start, then see <A
HREF="cygwin-x-faq.html#q-error-font-eof"
>Q: 9.4.</A
>
for information on how to fix your fonts.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-procedure-entry-point-missing"
></A
><B
>9.6. </B
><SPAN
CLASS="errorname"
>The procedure entry point _check_for_executable could
not be located</SPAN
></P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>This question should be obsolete.</P
><P
>Programs that you are attempting to use were compiled against a
newer version of Cygwin than is currently on your system.  Run
Cygwin's setup program to update your installation to the latest
version.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="cygX11-6.dll-missing"
></A
><B
>9.7. </B
>cygX11-6.dll not found after installation or upgrade</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>This question should be obsolete.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-status-access-violation"
></A
><B
>9.8. </B
><SPAN
CLASS="errorname"
>Exception: STATUS_ACCESS_VIOLATION</SPAN
></P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
<UL
COMPACT="COMPACT"
><LI
><P
>&#13;It is believed that this may have the same underlying causes as <A
HREF="cygwin-x-faq.html#q-fork-failures"
>Q: 9.16.</A
>
</P
></LI
><LI
><P
><TT
CLASS="filename"
>cygwin1.dll</TT
> uses a shared memory section
amongst all loaded copies of <TT
CLASS="filename"
>cygwin1.dll</TT
>;
unfortunately, the layout and usage of the shared memory section
changes between versions of <TT
CLASS="filename"
>cygwin1.dll</TT
>.
Loading two different versions of <TT
CLASS="filename"
>cygwin1.dll</TT
>
will cause the shared memory section to become corrupted, which almost
always results in an <SPAN
CLASS="errorname"
>Exception:
STATUS_ACCESS_VIOLATION</SPAN
>.  You must search your
filesystem(s) and remove all copies of
<TT
CLASS="filename"
>cygwin1.dll</TT
> except the copy in <TT
CLASS="filename"
>/bin</TT
>.  You must remove the different
versions of <TT
CLASS="filename"
>cygwin1.dll</TT
> even if they are not in
your path, as programs that depend on
<TT
CLASS="filename"
>cygwin1.dll</TT
> attempt to load the file from the
local directory before searching other paths; thus, it is rather easy,
and common, for multiple versions of <TT
CLASS="filename"
>cygwin1.dll</TT
>
to become loaded at the same time if they exist on a particular
system.</P
></LI
><LI
><P
>&#13;See also <A
HREF="http://cygwin.com/faq.html#faq.setup.setup-fails-on-ts"
TARGET="_top"
>&#13;this main Cygwin FAQ question</A
> for an issue which may cause this
problem with older binaries on Terminal Server.
</P
></LI
></UL
>
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-error-max-clients"
></A
><B
>9.9. </B
><SPAN
CLASS="errorname"
>Xlib: connection to
"<TT
CLASS="replaceable"
><I
>local_host_name_or_ip_address</I
></TT
>:0.0" refused
by server Xlib: Maximum number of clients reached</SPAN
></P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Cygwin/X queries getdtablesize() for the maximum number of
client connections allowed; by default Cygwin returns 32 from
getdtablesize().  Cygwin/X <A
HREF="http://x.cygwin.com/devel/server/"
TARGET="_top"
>Server Test Series</A
> release
<A
HREF="http://x.cygwin.com/devel/server/changelog.html"
TARGET="_top"
>Test44</A
>,
released on 2001-08-15, changed the maximum number of clients from 32
to 1024 by passing the square of getdtablesize() to setdtablesize().
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-xio-fatal-io-error-104"
></A
><B
>9.10. </B
><SPAN
CLASS="errorname"
>XIO: fatal IO error 104 (Connection reset by peer) on
 X server "127.0.0.1:0.0"</SPAN
></P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>See <A
HREF="cygwin-x-faq.html#q-error-max-clients"
>Q: 9.9.</A
></P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-cannot-open-display"
></A
><B
>9.11. </B
><SPAN
CLASS="errorname"
>Cannot Open Display: 127.0.0.1:0.0</SPAN
></P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Certain classes of software, such as that used for <A
HREF="glossary.html#gloss-vpn"
><I
CLASS="glossterm"
>Virtual Private Networking</I
></A
> and
<A
HREF="glossary.html#gloss-firewall"
><I
CLASS="glossterm"
>fire-walling</I
></A
> may cause
the IP address 127.0.0.1, or other local adapter addresses, to be
redirected, to become inoperable in some way, or to be operated in a
manner that violates the defined operation of IP address.</P
><P
>As a potential remedy, try removing all instances of such
software; this may not always fix the problem though, as some software
may leave artifacts even after uninstallation is completed.  The only
way to be sure that you have not found a Cygwin/X bug is to install
Windows on a freshly formatted hard drive, followed by Cygwin and
Cygwin/X, and finally add your other software one application at a
time until Cygwin/X stops working.</P
><P
>Some products that have been reported to cause problems:

<UL
COMPACT="COMPACT"
><LI
><P
><SPAN
CLASS="application"
>Aventail Connect</SPAN
></P
></LI
><LI
><P
><SPAN
CLASS="application"
>Zonealarm PC Firewall</SPAN
> from Zonelab</P
></LI
></UL
>

<DIV
CLASS="note"
><BLOCKQUOTE
CLASS="note"
><P
><B
>Note: </B
>These products may not cause problems in all configurations.
However, the Cygwin/X project has neither the time, ability, nor
resources to help you correctly configure your third-party
software.</P
></BLOCKQUOTE
></DIV
>

See <A
HREF="http://cygwin.com/faq.html#faq.using.bloda"
TARGET="_top"
>&#13;the main Cygwin FAQ question</A
> for an up-to-date list of software
which has been known to interfere with the correct operation of Cygwin.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-error-env-space"
></A
><B
>9.12. </B
>Out of environment space</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Increase your Windows environment space by following the <A
HREF="http://support.microsoft.com/support/kb/articles/Q230/2/05.ASP"
TARGET="_top"
>instructions
provided by Microsoft</A
>.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-too-many-parameters"
></A
><B
>9.13. </B
>Too many parameters</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>See <A
HREF="cygwin-x-faq.html#q-error-env-space"
>Q: 9.12.</A
></P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-xcb-lock-assertion"
></A
><B
>9.14. </B
>
"xcb_xlib_lock: Assertion '!c-&gt;xlib.lock' failed." or "xcb_xlib_unlock: Assertion 'c-&gt;xlib.lock' failed."
</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>This question should be obsolete.</P
><P
>&#13;Both of these represent bugs in a caller of libX11, and <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>not</I
></SPAN
> in libX11
or libxcb. The first assertion means that a caller attempted to lock
the display while already locked. The second assertion means that a
caller attempted to unlock the display without having it locked. 
</P
><P
>&#13;If you encounter such bugs, please report a bug against the offending 
software (which is <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>not</I
></SPAN
> libX11 or libxcb)
</P
><P
>&#13;This error can be worked around by using <B
CLASS="command"
>export LIBXCB_ALLOW_SLOPPY_LOCK=1</B
>
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-failed-to-compile-keymap"
></A
><B
>9.15. </B
>Fatal server error: Failed to activate core devices.</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
<TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="screen"
>&#13;(EE) XKB: Could not invoke xkbcomp
(EE) XKB: Couldn't compile keymap
XKB: Failed to compile keymap
Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.
Fatal server error: Failed to activate core devices.
</PRE
></TD
></TR
></TABLE
>

<UL
COMPACT="COMPACT"
><LI
><P
>&#13;Verify that xkeyboard-config is correctly installed using <B
CLASS="command"
>cygcheck -c xkeyboard-config</B
>,
</P
></LI
><LI
><P
>&#13;Check that <B
CLASS="command"
>/usr/bin/xkbcomp</B
> can be run from a bash shell.  If that fails, see if
<B
CLASS="command"
>cygcheck /usr/bin/xkbcomp</B
> reports any missing DLLs.
</P
></LI
><LI
><P
>&#13;Something is interferring with the ability of the X server to invoke <B
CLASS="command"
>xkbcomp</B
>
to compile the keymap.
</P
><P
>&#13;See <A
HREF="cygwin-x-faq.html#q-fork-failures"
>Q: 9.16.</A
> for possible causes.
</P
></LI
></UL
>

</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-fork-failures"
></A
><B
>9.16. </B
>"fatal error - unable to remap (some dll) to same address as parent: (some hex number) != (some other hex number)" or
"(some dll): Loaded to different address: parent(some hex number) != child(some other hex number)"</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
This is commonly caused by one of three things:
<UL
COMPACT="COMPACT"
><LI
><P
>&#13;You have run Cygwin's setup program to do an update while some
cygwin processes were running, and then clicked on the continue option in the
"In-use files detected" dialog, and then tried to carry on using Cygwin without
rebooting as advised by setup.  Reboot.
</P
></LI
><LI
><P
>&#13;This is one of the symptoms of an application interfering with Cygwin's fork() emulation.
See <A
HREF="http://cygwin.com/faq.html#faq.using.bloda"
TARGET="_top"
>&#13;the main Cygwin FAQ question</A
> for a list of software
which has been known to interfere with the correct operation of Cygwin.
</P
></LI
><LI
><P
>&#13;This also caused by DLLs with conflicting base addresses preventing Cygwin's fork() emulation
from functioning correctly.
See <A
HREF="http://cygwin.com/faq.html#faq.using.fixing-fork-failures"
TARGET="_top"
>&#13;the main Cygwin FAQ question</A
> for advice.
</P
></LI
></UL
>
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-died-waiting-for-longjmp"
></A
><B
>9.17. </B
>fork: child -1 - died waiting for longjmp before initialization, retry (some number), exit code (some hex number), errno (some other number)</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
This is believed to have the same underlying causes as <A
HREF="cygwin-x-faq.html#q-fork-failures"
>Q: 9.16.</A
>
</P
></DIV
></DIV
></DIV
><DIV
CLASS="qandadiv"
><H3
><A
NAME="porting"
></A
>10. Porting Software</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-ported-software-list"
></A
><B
>10.1. </B
>Is there a list of software that has been ported to Cygwin/X?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Look in Cygwin's setup program for packages in the X11 category.
</P
><P
>Also, see this <A
HREF="http://x.cygwin.com/ported-software.html"
TARGET="_top"
>Cygwin/X - Ported
Software</A
> old list.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-how-to-port"
></A
><B
>10.2. </B
>How do I start porting software to Cygwin/X?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Cygwin/X provides a software interface that is very similar to
the software interface provided by GNU/Linux and other <ACRONYM
CLASS="acronym"
>UNIX</ACRONYM
> systems.
Most software packages will compile on Cygwin/X without any changes
at all.  To begin with, try to compile a given software package
following that package's compilation instructions for GNU/Linux.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-common-porting-problems"
></A
><B
>10.3. </B
>Are there common problems encountered when porting software to
Cygwin/X?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>One common problem encountered when porting software to
Cygwin/X is due to Cygwin's inability to distinguish between files
with the same name but different capitalization (e.g. XvMC.h and
xvmc.h), which is due to a Windows' limitation.</P
><DIV
CLASS="example"
><A
NAME="example-include-problems"
></A
><P
><B
>Example 1. Include Problems</B
></P
><P
>This example is based off an error that actually occurred in the
source code tree in
<TT
CLASS="filename"
>xc/programs/Xserver/Xext/xvmc.c</TT
>.
<TT
CLASS="filename"
>xvmc.c</TT
> included <TT
CLASS="filename"
>XvMC.h</TT
>, as
shown below:</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="programlisting"
>&#13;#include "XvMC.h"
</PRE
></TD
></TR
></TABLE
><P
>The intention was to include the file
<TT
CLASS="filename"
>xc/include/extensions/XvMC.h</TT
>.  Unfortunately,
there was a file named
<TT
CLASS="filename"
>xc/programs/Xserver/Xext/xvmc.h</TT
> that ended up
getting included instead of the desired file, because the precompiler
searched the local directory, <TT
CLASS="filename"
>xc/programs/Xserver/Xext/</TT
>, before
searching the rest of the include path.  Cygwin can't distinguish
between <TT
CLASS="filename"
>XvMC.h</TT
> and <TT
CLASS="filename"
>xvmc.h</TT
>,
so <TT
CLASS="filename"
>xvmc.h</TT
> ended up being included in
<TT
CLASS="filename"
>xvmc.c</TT
>.  The build process on Cygwin broke
because the contents of <TT
CLASS="filename"
>XvMC.h</TT
> were entirely
different than the contents of <TT
CLASS="filename"
>xvmc.h</TT
>.</P
><P
>The solution was to change the include to specifically reference
the desired header:</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="programlisting"
>&#13;#include "../../../include/extensions/XvMC.h"
</PRE
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-opengl-link-problems"
></A
><B
>10.4. </B
>Problems linking OpenGL applications? Undefined reference to _gl<SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>something</I
></SPAN
>?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Cygwin has two OpenGL implementations:
</P
><OL
TYPE="1"
><LI
><P
>&#13;headers in /usr/include/w32api/GL, libraries (-lglut32 -lglu32 -lopengl32) from the opengl and w32api packages
which are for displaying
OpenGL graphics directly through the native Windows interface (Win32) without any X server
</P
></LI
><LI
><P
>&#13;headers in /usr/include/GL, libraries (-lglut -lglu -lgl) from the Mesa libGL packages
(libGL-devel, libGL1, libGLU-devel, libGLU1, libglut-devel, libglut3, freeglut)
which are for displaying OpenGL graphics through an X server.
</P
></LI
></OL
><P
>&#13;These are incompatible, even the headers (as the native OpenGL API has the stdcall calling convention),
so you must exercise care if you have both sets of devel packages installed.  An application must be built using only one of these.
</P
><UL
COMPACT="COMPACT"
><LI
><P
>X applications using GLX must be built using option 2.</P
></LI
><LI
><P
>Applications using GLUT have a choice.</P
></LI
><LI
><P
>Applications using the WGL API must be built using option 1.</P
></LI
></UL
><P
>&#13;(Words adapted from an email by André Bleau)
</P
></DIV
></DIV
></DIV
><DIV
CLASS="qandadiv"
><H3
><A
NAME="contributing"
></A
>11. Contributing</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-instructions-for-contributing"
></A
><B
>11.1. </B
>Are there step-by-step instructions for contributing to
Cygwin/X?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Yes.  The <A
HREF="http://x.cygwin.com/docs/cg/cygwin-x-cg.html"
TARGET="_top"
>Cygwin/X Contributor's
Guide</A
> has step-by-step instructions for obtaining the source,
building the source, building debug versions of the source, and even
cross-compiling under Linux.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-editors"
></A
><B
>11.2. </B
>Are there editors for Windows that understand and
preserve <ACRONYM
CLASS="acronym"
>UNIX</ACRONYM
> end of line characters?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Yes.  <SPAN
CLASS="application"
>Emacs</SPAN
> and
<SPAN
CLASS="application"
>XEmacs</SPAN
> are available for Windows; they both
understand and preserve <ACRONYM
CLASS="acronym"
>UNIX</ACRONYM
> end of line
characters.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-contrib-diff"
></A
><B
>11.3. </B
>How should I generate patches for Cygwin/X?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Only submit patches that have <ACRONYM
CLASS="acronym"
>UNIX</ACRONYM
> end of
line characters.  See <A
HREF="cygwin-x-faq.html#q-editors"
>Q: 11.2.</A
> for information on
editors for Windows that are aware of <ACRONYM
CLASS="acronym"
>UNIX</ACRONYM
> end of
line characters.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-where-to-submit-patches"
></A
><B
>11.4. </B
>Where do I submit patches for Cygwin/X?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Submit patches for Cygwin/X to the cygwin@cygwin.com mailing
list.</P
><P
>See <A
HREF="cygwin-x-faq.html#q-contrib-diff"
>Q: 11.3.</A
> for more information on
generating patches.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-why-no-autoconf"
></A
><B
>11.5. </B
>Why doesn't the X Window System use GNU's
<B
CLASS="command"
>autoconf</B
>?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>It does!  Thanks to the excellent efforts of the X.Org community,
the X Window System has been autotoolized since X.Org R7.0.
</P
><P
>&#13;Anyone who despaired of touching the monolithic tree will find things 
much easier now with modular packages.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-which-compilers-supported"
></A
><B
>11.6. </B
>What compiler does Cygwin/X use, and which compilers are
supported?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Cygwin/X uses the <SPAN
CLASS="application"
>gcc</SPAN
> compiler from
the Free Software Foundation.  Cygwin/X source code is mostly ANSI C
compliant, but we cannot guarantee that Cygwin/X will compile with
any other compiler, nor can we afford the time to support compilers
other than <SPAN
CLASS="application"
>gcc</SPAN
>.</P
><P
>See the <A
HREF="http://gcc.gnu.org"
TARGET="_top"
>GCC Home Page</A
> for more
information on <SPAN
CLASS="application"
>gcc</SPAN
>.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-cross-compiling"
></A
><B
>11.7. </B
>Is cross-compiling from a non-Cygwin platform supported?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Cross-compiling from a non-Cygwin platform is described in the
<A
HREF="http://x.cygwin.com/docs/cg/cygwin-x-cg.html"
TARGET="_top"
>Cygwin/X Contributor's
Guide</A
></P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-help-installing-docbook"
></A
><B
>11.8. </B
>Where can I get help for installing DocBook on Cygwin?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>The required packages are listed in the
<A
HREF="http://x.cygwin.com/docs/cg/cygwin-x-cg.html"
TARGET="_top"
>Cygwin/X Contributor's Guide</A
>.
</P
></DIV
></DIV
></DIV
><DIV
CLASS="qandadiv"
><H3
><A
NAME="license-ptc"
></A
>12. Licenses, Patents, Trademarks, and Copyrights</H3
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-what-licenses-apply"
></A
><B
>12.1. </B
>What licenses apply to Cygwin/X source code?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Cygwin/X proper isn't covered by a single license, as Cygwin/X
is made up of two parts that are covered by distinct licenses:
Cygwin and the X Window System.</P
><P
>See <A
HREF="cygwin-x-faq.html#q-license-x-window-system"
>Q: 12.2.</A
> and <A
HREF="cygwin-x-faq.html#q-license-cygwin"
>Q: 12.3.</A
> for more information regarding the
licenses that apply to Cygwin/X.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-license-x-window-system"
></A
><B
>12.2. </B
>What licenses apply to the X Window System source code?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>X Window System source code is generally licensed under an
<A
HREF="http://cgit.freedesktop.org/xorg/xserver/tree/COPYING"
TARGET="_top"
>X11 style license</A
>, which is
<A
HREF="http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses"
TARGET="_top"
>certified by the Free Software
Foundation</A
> as compatible with the <ACRONYM
CLASS="acronym"
>GNU</ACRONYM
>
<ACRONYM
CLASS="acronym"
>GPL</ACRONYM
>.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-license-cygwin"
></A
><B
>12.3. </B
>What license applies to Cygwin source code?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Cygwin source code is
<A
HREF="https://cygwin.com/licensing.html"
TARGET="_top"
>&#13;licensed under a modified version of the
<ACRONYM
CLASS="acronym"
>GNU</ACRONYM
> <ACRONYM
CLASS="acronym"
>GPL</ACRONYM
>
</A
>.
Cygwin's license
modification specifically allows third-party software under an
<A
HREF="http://opensource.org/licenses"
TARGET="_top"
>&#13;open source license
</A
>
to be linked with Cygwin without requiring that the
source code for the third-party software be distributed under the
terms of the <ACRONYM
CLASS="acronym"
>GNU</ACRONYM
> <ACRONYM
CLASS="acronym"
>GPL</ACRONYM
>.
Cygwin's developers went to great trouble to obtain this
modification and should be thanked for doing so, as without it the
modification, Cygwin/X linking to Cygwin would be the subject of
endless discussion.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-copyright-cygwin-x"
></A
><B
>12.4. </B
>Who holds the copyright on the Cygwin/X source code?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Cygwin/X proper doesn't have a single copyright holder, as
Cygwin/X is made up of two parts, namely Cygwin and the
X Window System; each part follows a different scheme in regards to
who will hold the copyright on source code.</P
><P
>See <A
HREF="cygwin-x-faq.html#q-copyright-x-window-system"
>Q: 12.5.</A
> and <A
HREF="cygwin-x-faq.html#q-copyright-cygwin"
>Q: 12.6.</A
> for more information regarding who
holds the copyright on Cygwin/X source code.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-copyright-x-window-system"
></A
><B
>12.5. </B
>Who holds the copyright on the X Window System source code?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Each source code file in the X Window System typically has its
own license and copyright statement.  Therefore, there is not a
general rule for determining who holds the copyright on a particular
X Window System source file, as each author is free to assign the
copyright to someone else, to some group, or to keep the copyright
themselves.  You must inspect the source code file in question to
determine who holds the copyright for that file.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-copyright-cygwin"
></A
><B
>12.6. </B
>Who holds the copyright on the Cygwin source code?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
><A
HREF="http://redhat.com/"
TARGET="_top"
>Red Hat</A
> owns the copyright
on the Cygwin source code.  Red Hat requires that copyright be
assigned to Red Hat for non-trivial changes to Cygwin.  You must
fill out a copyright transfer form if you are going to contribute
substantial changes to Cygwin.</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-motif-license"
></A
><B
>12.7. </B
>What license applies to Motif?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>
Motif is a product of <A
HREF="http://www.opengroup.org/"
TARGET="_top"
>The Open Group</A
>.
After many years under the
<A
HREF="http://www.opengroup.org/openmotif/license"
TARGET="_top"
>The Open Group Public License</A
>
(which does not satisfy the
<A
HREF="http://opensource.org/docs/osd/"
TARGET="_top"
>Open Source Definition</A
>
and is thus not compatible with Cygwin's license),
Motif was released as free software under the LGPL v2.1 in October 2012.
</P
></DIV
></DIV
><DIV
CLASS="qandaentry"
><DIV
CLASS="question"
><P
><A
NAME="q-trademark-xwin"
></A
><B
>12.8. </B
>Isn't <SPAN
CLASS="QUOTE"
>"XWin"</SPAN
> trademarked by StarNet Communications?</P
></DIV
><DIV
CLASS="answer"
><P
><B
> </B
>Not in the USA, at least.  A quick search at the <A
HREF="http://www.uspto.gov/"
TARGET="_top"
>United States Patent and Trademark Office</A
> for <SPAN
CLASS="QUOTE"
>"XWin"</SPAN
> turns up
one dead record and one live record.  The live record is for a logo
belonging to a rock crusher manufacturer based out of Belgium.
Neither trademark affects Cygwin/X, as the dead record is no longer
enforceable, while the live record is in an unrelated and distinct
industry; there cannot be confusion between rock crushers and computer
programs.</P
></DIV
></DIV
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"/><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="biblio.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Bibliography</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>